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:\Program Files\Ground Zero Tech-Works Inc\AyaNova 3

Error details:
Unhandled Exception:
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
System.Net.WebException
Inner exception: The remote certificate is invalid according to the validation procedure.

Stack Trace:

Server stack trace:
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream)
   at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

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()

Tom Demmitt

I have not encountered this message before.

1. What version of AyaNova is in use (log into AyaNova, select menu Help -> About AyaNova)

2. What file versions of Data Portal are in use? open Windows Explorer, open C:\Inetpub\wwwroot\AyaNovaDP\bin folder and find the file GTZW.AyaNova.BLL.dll:

• - what is the file date of this file?
•  - right-click on this file, select Properties, and provide the version for this file

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

1) The version of Ayanova that I am using is the latest. it says 3.4.3.0

2) The file GTZW.Ayanova.BLL.dll ver is 3.4.2.0

Thanks

Tom Demmitt

As we have two things happening - a WBI issue plus a Data Portal issue - I'm leaning towards something with IIS - but if you can provide the requested in my post on http://forum.ayanova.com/Topic2959-95-1.aspx we will start will those, and go from there.

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

The configuration file is using https:// instead of http:// as in :

<add key="PortalServer" value="https://website.com/AyaNovaDP/DataPortal.rem" />

whereas the config line should be as:

<add key="PortalServer" value="http://website.com/AyaNovaDP/DataPortal.rem" />

Once the config file was edited, the following error occurs trying to connect to the database via DataPortal

Error details:
Unhandled Exception:
Unable to connect to the remote server
System.Net.WebException
Inner exception: No connection could be made because the target machine actively refused it

This message can be a result of many different causes - first is to confirm that the URL is actually correct.  Am presently awaiting response on what the actual external IP address and port number for the IIS server connection is from Tom as well as additional information requested in the corresponding topic http://forum.ayanova.com/Topic2959-95-1.aspx

If anyone has experienced this type of error and would like to post their solution, that is always welcome too.

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

1. AyaNovaDP sites Properties in the Directory Security tab had Secure Communications enabled when should be set as below:

2. AyaNova.exe.config file used by the remote user was incorrectly using https:// in the URL as identified in the posting above

3. AyaNova.exe.config file used by the remote user was incorrectly pointing to an invalid site name - resulting in the error   "Inner exception: No connection could be made because the target machine actively refused it - once the actual web site name/ip address was used, able to log in.

AyaNova Sales & Technical Support

http://www.ayanova.com