Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Login problems with trusted application

Status
Not open for further replies.

LectorDK

ISP
Mar 2, 2004
4
DK
Hi, we are working on a program that use the trusted application method to log on to Groupwise.
For some odd reason, it's not possible to log on with all users, even though they're all created in exactly the same way.
We have two test servers, and on one about 90% of the accounts work, while on the other it's about 50% that works.
All accounts can log on to groupWise using the GroupWise client - so it's only the trusted application method that gives us problems.
Does anyone know what could be wrong here, and hopefully, what we can do to get all accounts working.
Cheers!
 
What are, if any, error code(s)/description(s) returned for the users not getting logged on?

FarOut
V-Peace-V
 
We just get a "Logon failed" message with com+ result code -532459699 and hresult code 2146232828.
However, we can log on as that user through the GroupWise client.
If has any influence, we use C# and .NET framework version 1.1.

 
Here's the .NET stack trace for more details:

[COMException (0x80004005): Logon failed]
System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData) +457
GroupwareTypeLibrary.Application3Class.MultiLogin(String vUserID, Object vCommandLine, Object vPassword, Object vWhenToPrompt, Object vReserved) +0

 
Can you compare the userid string being passed for a user that can login, versus the userid string for a user that can not login?

FarOut
V-Peace-V
 
The code called for each login is exactly the same, the only thing that changes is the user name.
We uses a fixed server IP and port number, as it's a trusted app, there's no password. So connection info is the same (apart from the username) on users that succeed and users that fail.
And that's our big problem - there are no differences between the two kind of users.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top