Curse Client v4 - Windows

818 - Cannot login repost

Submitted Via

Curse Client 4.0.0.617, Microsoft Windows NT 6.0.6001 Service Pack 1

Username

Brathinox

Description

Reposting Unknown Login error problem with version 4.0.0.617

Game Configuration

Game Type: World of Warcraft
Game Path: F:\World of Warcraft\
Addon Path: F:\World of Warcraft\interface/addons
Folder Count: 154
Addon Count: 30
Scanning Security Exceptions: 0
Scanning Unknown Exceptions: 0
Scanning Empty Directories: 23
Scanning Directories Not Found: 0

Game Type: Runes of Magic
Game Path: F:\Runes of Magic\
Addon Path: F:\Runes of Magic\interface/addons
Folder Count: 1
Addon Count: 1
Scanning Security Exceptions: 0
Scanning Unknown Exceptions: 0
Scanning Empty Directories: 0
Scanning Directories Not Found: 0

Log Data

Curse Client Starting...

Version 4.0.0.617

Task Executing: Firewall

Task Executing: Connection

Task Executing: GameDatabase

Task Executing: AddOnDatabase

Task Executing: GameInstalls

Task Executing: Core

Startup Complete

CClientLogin - Login Exception!
Exception Details: Message:Client is unable to finish the security negotiation within the configured timeout (00:09:59.9980000). The current negotiation leg is 1 (00:09:59.9700000).
Stack Trace:
Server stack trace:
at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)
at System.ServiceModel.Security.SspiNegotiationTokenProvider.OnOpen(TimeSpan timeout)
at System.ServiceModel.Security.TlsnegoTokenProvider.OnOpen(TimeSpan timeout)
at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Security.SecurityUtils.OpenCommunicationObject(ICommunicationObject obj, TimeSpan timeout)
at System.ServiceModel.Security.SymmetricSecurityProtocol.OnOpen(TimeSpan timeout)
at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)
at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

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 Curse.CurseClient.Common.ClientService.CClientService.LoginUser(String username)
at Curse.CurseClient.Common.CServiceProxy.

Fault Details: Not a security fault.

User When Change
Adamar Tue, 15 Sep 2009 19:59:53 Changed status from New to Invalid
None Tue, 15 Sep 2009 19:50:59 Create

You must login to post a comment. Don't have an account? Register to get one!

  • 2 comments
  • 2 comments

Facts

Last updated on
15 Sep 2009
Reported on
15 Sep 2009
Status
Invalid - This was not a valid report.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.

Reported by

  • Avatar of
    Anonymous

Possible assignees