We are currently upgrading our powerbuilder project from PB8.0.4 to PB10.5.1. In version 8.0.4 we were able to successfully connect to a SourceOffSite server as our source control provider. Upon migrating to PB10.5.1, PB crashes when attempting to sign in to the same SoS server. My local version of the SoS client is 4.1.2.242. Here is the server information:
SoS Client: version 4.1.2.185
SoS Service: version 4.1.2.184
VSS ssapi.dll: version 6.0.93.50
It appears the login is successful in the PB IDE, but fails upon initialization. Has anyone had any experience with this problem?
Here is the log from the SOS server log.txt:
3/19/2007 3:02:53 PM - Connection accepted from xxx.xx.xx.xx:xxxx on local address xxx.xxx.xx.xx:xxxx, session id is 1.
3/19/2007 3:02:54 PM - 1: Connection from: computername (xxx.xx.xx.xx)
3/19/2007 3:02:54 PM - 1: Preparing to send the list of databases...
3/19/2007 3:02:54 PM - 1: Sending the challenge to the client.
3/19/2007 3:02:54 PM - 1: Sending the challenge message body to the client.
3/19/2007 3:02:54 PM - 1: Waiting for the client's response...
3/19/2007 3:02:59 PM - 1: Reviewing the client's response...
3/19/2007 3:02:59 PM - 1: Process the client's crypto login request.
3/19/2007 3:02:59 PM - 1: User 'username' requesting to login to database '\\server\SourceSafeLib\srcsafe.ini'
3/19/2007 3:02:59 PM - 1: Client is speaking protocol version 2.0
3/19/2007 3:02:59 PM - 1: Attempting to login WITH crypto.
3/19/2007 3:02:59 PM - 1: Verify the challenge string.
3/19/2007 3:02:59 PM - 1: Get the session key.
3/19/2007 3:02:59 PM - 1: Open the database.
3/19/2007 3:02:59 PM - 1: 'username' connected to database \\server\SourceSafeLib\srcsafe.ini
3/19/2007 3:03:00 PM - 1: Received message number 102.
3/19/2007 3:03:00 PM - 1: Ignore remote dates = True
3/19/2007 3:03:00 PM - 1: GetFileList project: $/Project/Pbl
3/19/2007 3:03:00 PM - 1: Time to execute: 0 minutes, 0 seconds, 218 milliseconds.
3/19/2007 3:03:04 PM - 1: Exception: An existing connection was forcibly closed by the remote host
3/19/2007 3:03:04 PM - 1: Error processing client request: at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at ClassicService.ProtocolMessage.ParseStream(Socket socket, Crypto crypto)
at ClassicService.Client.GetMessage()
3/19/2007 3:03:04 PM - 1: User username disconnected from computername.
SOS connection causes Powerbuilder 10.5.1 to crash
Moderator: SourceGear
If the SOS standalone client is working fine, then there's some problem with the IDE integration. We don't support integration with PowerBuilder, so we can't be of much help in diagnosing the problem.
Although PowerBuilder may use the same integration .dll as Visual Studio (which we do support), the sequence of calls may be different, etc.
You could use SOS client for source control operations, such as checkout, checkin, etc., and continue your development in PowerBuilder.
If any SOS users have experience with PowerBuilder 10, please post here.
Although PowerBuilder may use the same integration .dll as Visual Studio (which we do support), the sequence of calls may be different, etc.
You could use SOS client for source control operations, such as checkout, checkin, etc., and continue your development in PowerBuilder.
If any SOS users have experience with PowerBuilder 10, please post here.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager