Been using 3.5 for months...love it.

Today we had to restart our server for updates and for another reason and when it came back up we got the following error:

AyaNova was unable to start

Depending on how early in startup the problem occurred,
a detailed log of the problem with suggestions *may* have
been saved to the file AyaLog.txt
located at: file:\C:\Ayanova_v3

Error details:
Unhandled Exception:
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException
Inner exception: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Stack Trace:
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at CSLA.Server.DataPortal.CallMethod(Object obj, String method, Object[] params)
   at CSLA.Server.DataPortal.Fetch(Object Criteria, DataPortalContext context)
   at CSLA.DataPortal.Fetch(Object Criteria)
   at CSLA.Security.BusinessIdentity.LoadIdentity(String UserName, String Password)
   at CSLA.Security.BusinessPrincipal..ctor(String Username, String Password)
   at CSLA.Security.BusinessPrincipal.Login(String Username, String Password)
   at GZTW.AyaNova.BLL.AyaBizUtils.0()
   at GZTW.AyaNova.BLL.AyaBizUtils.Initialize()
   at AyaNova.Form1.0()

Can't seem to be able to determine what caused this.  Any ideas?

THanks,

Need Help

I did a search for that error message on the Internet When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes Provider,error:40-Could not open connection to SQL Server)) , and found this great site at  http://www.datamasker.com/SSE2005_NetworkCfg.htm showing what you should check that TCP/IP protocol is set up via the Surface Area Configuration Utility, TCP/IP protocol is enabled in the SQL Server Configuration Utility, making sure the SQL Server browser is started and making sure SQL Server and SQL Server Browser are exempted by the firewall on the server machine

Sometimes updates can re-enable or blow away previous Firewall exceptions, so I would check that first.

Simpliest test is to ensure the Firewall is turned off completely, than try again. If you can now connect, than you know your Firewall is the problem, and than do as that link says to do.

Otherwise, check the other items listed in that link I put above, and do post your results back.

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com