yes, using correct login. Debug view is below. It states something about times not synchronized. There is a 7 minute difference between my server and my PC.
CounterSoft Gemini: Logon Exception. WSE065: Creation time of the timestamp is in the future. This typically indicates lack of synchronization between sender and receiver clocks. Make sure the clocks are synchronized or use the timeToleranceInSeconds element in the microsoft.web.services3 configuration section to adjust tolerance for lack of clock synchronization.
00000000 0.00000000 [3316] CounterSoft Gemini: Start DoLogin
00000001 0.00654369 [3316] CounterSoft Gemini: Checking Model.Authenticated
00000002 0.00658759 [3316] CounterSoft Gemini: Checking offline setting
00000003 0.00672907 [3316] CounterSoft Gemini: Checking webservices URL suffix: http://web02/gemini/
00000004 0.00682331 [3316] CounterSoft Gemini: Starting logon process
00000005 0.00687541 [3316] CounterSoft Gemini: Calling ServiceHelper.AuthorisationServicesLogIn
00000006 0.52709520 [3316] CounterSoft Gemini: Exception caught during logon!
00000007 0.52712446 [3316] CounterSoft Gemini: Logon Exception. WSE910: An error happened during the processing of a response message, and you can find the error in the inner exception. You can also find the response message in the Response property. :: Microsoft.Web.Services3 :: at Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage message, String messageContentType)
00000008 0.52712446 [3316] at Microsoft.Web.Services3.WebServicesClientProtocol.GetReaderForMessage(SoapClientMessage message, Int32 bufferSize)
00000009 0.52712446 [3316] at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
00000010 0.52712446 [3316] at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
00000011 0.52712446 [3316] at AuthorisationServices.LogIn(String userName, String password)
00000012 0.52712446 [3316] at CounterSoft.Gemini.Client.Commons.Helpers.ServiceHelper.AuthorisationServicesLogIn(GeminiModel model, String sUserName, String sPassword)
00000013 0.52712446 [3316] at CounterSoft.Gemini.Client.UI.Presenters.LoginPresenter.DoLogin()
00000014 0.52727818 [3316] CounterSoft Gemini: Logon Exception. An error was discovered processing the header :: Microsoft.Web.Services3 :: at Microsoft.Web.Services3.Security.Utility.Timestamp.CheckValid()
00000015 0.52727818 [3316] at Microsoft.Web.Services3.Security.Utility.Timestamp.LoadXml(XmlElement element)
00000016 0.52727818 [3316] at Microsoft.Web.Services3.Security.Utility.Timestamp..ctor(XmlElement element)
00000017 0.52727818 [3316] at Microsoft.Web.Services3.Security.Security.LoadXml(XmlElement element)
00000018 0.52727818 [3316] at Microsoft.Web.Services3.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope)
00000019 0.52727818 [3316] at Microsoft.Web.Services3.Security.Wse2PipelinePolicy.LegacyFilterWrapper.ProcessMessage(SoapEnvelope envelope)
00000020 0.52727818 [3316] at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
00000021 0.52727818 [3316] at Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage message, String messageContentType)
00000022 0.52731717 [3316] CounterSoft Gemini: Logon Exception. WSE065: Creation time of the timestamp is in the future. This typically indicates lack of synchronization between sender and receiver clocks. Make sure the clocks are synchronized or use the timeToleranceInSeconds element in the microsoft.web.services3 configuration section to adjust tolerance for lack of clock synchronization. :: ::
00000023 0.52744442 [3316] CounterSoft Gemini: Logon Exception. An error was discovered processing the header :: Microsoft.Web.Services3 :: at Microsoft.Web.Services3.Security.Utility.Timestamp.CheckValid()
00000024 0.52744442 [3316] at Microsoft.Web.Services3.Security.Utility.Timestamp.LoadXml(XmlElement element)
00000025 0.52744442 [3316] at Microsoft.Web.Services3.Security.Utility.Timestamp..ctor(XmlElement element)
00000026 0.52744442 [3316] at Microsoft.Web.Services3.Security.Security.LoadXml(XmlElement element)
00000027 0.52744442 [3316] at Microsoft.Web.Services3.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope)
00000028 0.52744442 [3316] at Microsoft.Web.Services3.Security.Wse2PipelinePolicy.LegacyFilterWrapper.ProcessMessage(SoapEnvelope envelope)
00000029 0.52744442 [3316] at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
00000030 0.52744442 [3316] at Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage message, String messageContentType)
00000031 0.52748287 [3316] CounterSoft Gemini: Logon Exception. WSE065: Creation time of the timestamp is in the future. This typically indicates lack of synchronization between sender and receiver clocks. Make sure the clocks are synchronized or use the timeToleranceInSeconds element in the microsoft.web.services3 configuration section to adjust tolerance for lack of clock synchronization. :: ::
00000032 0.55407870 [3316] CounterSoft Gemini: DoLogin End
00000033 5.61656904 [3476] NMAgent : Completed discovery of agents.
