May 29, 2009 at 2:58 pm
Or should I say that the code is never called.
Two different SQL 2005 x64 installations on Windows 2003 Server x64. Both
call a simple extended stored procedure from Query Analyzer. On one server it works
fine. On the other, almost identical server it never returns and the
instance hangs.
Debug code shows that the extended stored procedure code is never even
reached! (Although the "using dll" informational message does appear in the
log file.)
I suspected some kind of permissions problem, but the user is connected as a
sysadmin in both cases.
Any suggestions what to look for? Thanks.
May 29, 2009 at 3:16 pm
Which one is it? Or is it one of your own?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
May 29, 2009 at 5:26 pm
One of my own. Working flawlessly on almost all the machines except the one. Thanks.
May 29, 2009 at 5:57 pm
Is it possible to post the stored procedure? Do both SQL instances have same service packs too?Thanks.
June 5, 2009 at 10:39 am
I don't believe it is the extended stored procedure as the code is never even being reached. (First thing it does is write a log entry, which never appears).
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply