Thursday, February 09, 2012 ..:: Forums ::.. Register  Login
 Forums Minimize
 
ForumForumPlug-in and Pla...Plug-in and Pla...Outlook 2003 Pl...Outlook 2003 Pl...Unable to connect: Boolean Connect(Boolean) Line 733Unable to connect: Boolean Connect(Boolean) Line 733
Previous Previous
 
Next Next
New Post
 9/4/2006 5:48 AM
 

Hi,

I have SplendidCRM_Plug-in_for_Outlook_1.0.2436.2478_Final installed on Outlook 2003 SP2 on Windows XP SP2. I try to synchronize with splendidCRM Version 4.2.0 Build 1.2.2436.5039. When testing my connection ("Basic", whatever this means) to our splendidCRM server via Tools of the Outlook 2003 plugin, the test is ok. However when trying to syncronize e.g. contacts, the above error message displays. The complete error message is:

Boolean Connect(Boolean) Line 733.

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: The session ID is invalid

   at SplendidCRM.soap.GetSessionUserID(String session) in C:\Web.net\SplendidCRM2\soap.asmx.cs:Line 493

   at SplendidCRM.soap.get_user_id(String session) in C:\Web.net\SplandidCRM2\soap.asmx.cs:line 745

   --- End of inner exception stack trace ---

Thanks for any help.

Regards, Wolfram

New Post
 9/4/2006 7:57 PM
 

Is there any chance that the web server was restarted after Outlook connected?  The SplendidCRM web application stores the Session ID in the application Cache, with an expiration of 1 day.  The cache gets reset any time the web server gets restarted, so our natural thought is that the cache is getting reset unexpectedly.

The Outlook Plug-in supports two methods of authentication, Basic and Windows.  We recommend that you use Windows authentication so that you don't need to manage passwords in SplendidCRM. 

 

New Post
 9/5/2006 12:19 AM
 

Thank you for explaining the two methods of authentication.

That the web server was restarted after Outlook connected can be excluded. In my case the web server is up since installation of splendidCRM. There is however another phenomenon that puzzles me and may contribute to get the right picture. Each time I start Outlook I go to the "splendidCRM Settings" within Outlook to check, if I can connect to our server. To do this, I simply press "Test" in the "Authentication Options". This will always fail the first time, i.e. without changing anything in the window. After retyping my password it will always succeed. In the case of failure I get the following message:

Boolean Connect() Line 379.
System.Web.Service.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Invalid username and/or password
  at SplendidCRM.soap.LoginUser(String sUSER_NAME, String sPASSWORD) in C:\Web.net\SplendidCRM2\soap.asmx.cs:line 604
  at SplendidCRM.soap.create_session(String user_name, String password) in C:\Web.net\SplendidCRM2\soap.asmx.cs:line 620
  --- End of innter exception stack trace ---

This means the password has not been stored. This behaviour can be repeated within one Outlook session as many times as I want. Each time I close the  "splendidCRM Settings" window, the password seems to be lost. Is this behaviour by design? 

Kind Regards, Wolfram

New Post
 9/5/2006 8:57 AM
 
 Modified By Support  on 9/5/2006 8:04:44 AM

The password should indeed be remembered.  Thanks for the additional information.  We will continue to research this issue.

We store a hash of the password in: C:\Documents and Settings\[your login id]\Application Data\SplendidCRM\SplendidCRM Plug-in for Outlook.xml

Can you tell me if this matches the USER_HASH in the database.  The values are computed separately, but they should contain the same value.

 

 

New Post
 9/5/2006 12:52 PM
 

The hash code in my local xml-file and the hash code in USER_HASH are identical.

Regards, Wolfram

Previous Previous
 
Next Next
ForumForumPlug-in and Pla...Plug-in and Pla...Outlook 2003 Pl...Outlook 2003 Pl...Unable to connect: Boolean Connect(Boolean) Line 733Unable to connect: Boolean Connect(Boolean) Line 733


  
Copyright (c) 2006-2010 SplendidCRM Software, Inc. All Rights Reserved.   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2012 by DotNetNuke Corporation