Ed Leafe wrote:
> On Jun 18, 2007, at 7:51 PM, Bill Witherspoon wrote:
>
>> The problem turns out to be the host of "192.168.51.26:1433" vs.
>> "192.168.51.26". I added the following to pymssql.py and all is well:
>> (starting at line 341)
>>
>> if host != "":
>> dbhost = host.split(":")[0]
>> #print "pymssql dbhost = ",dbhost
>> #dbhost = host
>>
>> This effectively strips the port out of the host parameter. I'm not
>> sure
>> that this is the right fix, or the right place to this? Perhaps you
>> would know better. This would seem to eliminate any hope of Dabo/
>> pymssql
>> working with a Sql Server running on a non-standard port.
>
> The code in dbMsSQL deliberately puts the port in with the host, as
> that was the only way that it worked previously. So you're saying
> that your site only worked if the port was not part of the host?
>
Yes - the connection dialog now works using my SQL Auth user/pass
combination.
If I allow the port number - I get a 60 second time out followed by the
"No Connection" message. I confirmed this both by using the connection
dialog, and by hand coding the connection string with
host="192.168.51.26:1433". Removing the ":1433" creates success.
Possibly something changed in pymssql? I'm using version 0.8.0 released
2006-09, which isn't very recent.
I can do some further testing for you if you like.
Bill.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
