Problem posting Logs with hosted SELECTServer

Hi All,

We host our own SELECTServer, and for the last month we have been haing issues with the 'Usage Log Posting' task failing every day.  I thought it may have been our proxy server, but when have given this machine direct access to the Bentley servers and it still fails.

The Log file 'SS-UsageLogPostingService.log' contains the following messages.

03-05-13 13:50:37 INFO  - UsageLogPostingService - Checking if the UsageLogProcessingService is currently executing. Pause if so...
03-05-13 13:50:37 INFO  - UsageLogPostingService - UsageLogProcessingService is not executing. The Service will continue to execute.
03-05-13 13:50:37 INFO  - BussinessLogic - Found 0 sites to transmit logs for.
03-05-13 13:50:37 INFO  - BussinessLogic - TRANSMIT LOGS: 8 to transfer
03-05-13 13:50:58 ERROR - BUDDI - Request to Web Service [http://buddi.bentley.com/discovery.asmx] for regions failed.
03-05-13 13:51:19 ERROR - BUDDI - Request to Web Service [http://buddi.bentley.com/discovery.asmx] for regions failed.
03-05-13 13:52:01 ERROR - BUDDI - Request to Web Service [http://buddi.bentley.com/discovery.asmx] for regions failed.
03-05-13 13:52:01 ERROR - BussinessLogic - Could not send send logs to url [http://ssla.bentley.com/licensing.asmx]: Unable to connect to the remote server
03-05-13 13:52:01 ERROR - BussinessLogic - System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.30.230:3128
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Bentley.SelectServer.Common.Online.WebServices.Proxies.licensing.SubmitUsageLogs(String selectServerSerialNumber, String selectServerActivationKey, XmlNode concurrentUtilizationBySite, XmlNode usageProductByMachine, XmlNode usageProductByUser)
   at Bentley.SelectServer.BusinessLogic.CreatePostinglogs.PostLogs(String serverSerialNumber, String serverActivationKey, XmlNode concurrentUtilizationLog, XmlNode machineUsageLog, XmlNode userUsageLog)
03-05-13 13:52:01 ERROR - BussinessLogic - TRANSMIT LOGS: error posting log file record # 1 [Error Code: 1]
03-05-13 13:52:01 ERROR - BussinessLogic - Error posing Usages Logs
03-05-13 13:52:01 ERROR - UsageLogPostingService - Service Process Returned Error Code# -1 - An error occurred while sending logs to bentley.com

For some reason it is referencing our old proxy server (10.10.30.230), but I have remove the proxy setting from the application (and restarted the application and server).

I have tried the web service URLs directly in IE from the server and they both work.

I am running "SELECTserver V8i (SELECTseries 2) - Version 8.11.7.111".

Any ideas??

Thanks,

Ian

 

 

 

Parents
  • Hi Ian,

    I have seen this scenario before and it was resolved by changing the log on account for the Bentley SELECTserver service from Local System Account to a local administrator account. If that solves the issue you can set up a service account for the service or work out where the Local System Account is remembering the old proxy information.

    If that doesn't help, running Wireshark while attempting to post logs via the Manage Services option of the Administration site, may explain why the traffic is still going via 10.10.30.230. I have seen company's believe the proxy was being bypassed but a further exception was required somewhere in the environment.

    I hope that helps.

    Regards,

    Jim

Reply
  • Hi Ian,

    I have seen this scenario before and it was resolved by changing the log on account for the Bentley SELECTserver service from Local System Account to a local administrator account. If that solves the issue you can set up a service account for the service or work out where the Local System Account is remembering the old proxy information.

    If that doesn't help, running Wireshark while attempting to post logs via the Manage Services option of the Administration site, may explain why the traffic is still going via 10.10.30.230. I have seen company's believe the proxy was being bypassed but a further exception was required somewhere in the environment.

    I hope that helps.

    Regards,

    Jim

Children