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 3

Error details:
Unhandled Exception:
Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException
Inner exception: Unable to complete network request to host "70.233.225.9:6969".

Stack Trace:

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 System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   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()

Does anyone know why I am getting this??? 

I would suggest checking and doing the following:

• you have upgraded the Data Portal to 3.5.0.0 - correct? - compare file versions and dates to those that are in the AyaNova 3.5.0.0 program folder
• have you restarted IIS completely?
• have you rebooted the IIS server computer itself?
• go back through the steps of setting up a Data Portal where on the server you enter in the URL http://localhost:XXXX/AyaNovaDP/DataPortal.rem?wsdl - does that work on the server itself (where xxxx is the port number of IIS (doublecheck what the port should be for IIS)
• double-check what the external ip address and port number is to make sure someone or something has not changed it
• also enter the IP address instead of local host along with the confirmed port number - i.e.
• compare the Web.config connection string to that of an internal networked connection AyaNova.exe.config that is connecting to the database successfully - does it have the exact same connection to the same port number, same ip address, same username, same password?

Do post your results back what you find

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

Do post back the details.

If you determined the issue, do post what it was for the benefit of all.

Thank you

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

You can always email directly to support@ayanova.com at any time - support is usually provided the fastest via the forum, as well as being of benefit to other AyaNova users.

I was hoping that you would confirm the items listed in my previous reply as that may show you where the issue is. If you want to email me directly the information instead of posting, that is fine. But do provide the specific details.

I've listed them again below as well as identified even more so what I suggest checking:

• go back through the steps of setting up a Data Portal where on the server you enter in the URL http://localhost:XXXX/AyaNovaDP/DataPortal.rem?wsdl - does that work on the server itself (where xxxx is the port number of IIS (doublecheck what the port should be for IIS)
• double-check what the external ip address and port number is to make sure someone or something has not changed it
• also enter the IP address instead of local host along with the confirmed port number - i.e.
• compare the Web.config connection string to that of an internal networked connection AyaNova.exe.config that is connecting to the database successfully - does it have the exact same connection to the same port number, same ip address, same username, same password?

With the information that http://localhost:XXXX/AyaNovaDP/DataPortal.rem?wsdl & http://XXX.XXX.XXX.XXX:XXXX/AyaNovaDP/DataPortal.rem?wsdl work on the server  - when you entered in http://XXX.XXX.XXX.XXX:XXXX/AyaNovaDP/DataPortal.rem?wsdl was xxx.xxx.xxx.xxx:xxxx a local ip address? if so, what was it?, or did you enter the same external ip address identified in your first topic 70.233.225.9:6969 ?

Does entering the URL using 70.233.225.9:6969 in web browser when on the server work?

Is this 70.233.225.9 the IP address of your router? - double-check in case something has changed

Is 6969 the port you have opened on that router that is pointing to the internal ip address of the server? - double-check in case something has changed

Is the internal IP address of the server the exact same internal ip address identified in the router configuration? - double-check in case something has changed

Is 6969 the port identified for AyaNovaDP and the default web site in IIS on this server? - double-check in case something has changed

Is port 6969 been set up in this server's firewall to be allowed through? - double-check in case something has changed.

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

None of the information came across.

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com