problems with extended stored procedure
-
hey there,
I created an extended stored procdure in VC6++ under windows 200k prof and SQL Server Developer Edition. Every thing works fine in the development machine. However, there is a problem when I tried to deploy it to other machines. It does not work on SQL Server enterprise edition with error "Connection opened but invalid login packet(s) sent. Connection closed. Error: 17832, Severity: 20, State: 10". On some machines with SQL Server which its defualt port number is not 1433, it seems fail to connect to the server using the same user login infomation. I have no ideas what is missing here. Does anyone have any suggestions?
Thanks for any help.
-
We have run into this a few times, primarily with down-level and third-party clients, and usually in a situation where the server was requiring security but the client could not negotiate a secure TDS connection. This is a real long shot in the dark (to mix metaphors) but you might want to check the Server Network Utility on the server to make sure it's not requiring data encryption, and check the Client Network Utility on the client to make sure it's not requiring it either.
Like I said, it's a long shot, but it's worth taking a look.
Cheers,
Chris
-
Thanks Chris.
Yes, the SQL enterprise server has a Force Protocol Encryption option turned on. It is one of the standard requirements in the production environment, and I cannot simply turn it off just for a few functions from my extended stored procedures. If it is the reason that causes the problems, I think there must be some workarounds out there.
I also have some confuses here. My extended stored procedures reside in the SQL Server, and use client's login information to connect itself to the server and process data on behalf of the client. If the client can successfully login to the server, why the extended stored procedure cannot? I might misunderstand something here, please give me some help.
Thanks.
-
> I also have some confuses here.
That's my fault, I think, because you raise some good points that I didn't think of. I have very little experience developing extended stored procedures, so I think that I didn't really think through the points you raise about security context. Are you creating a new SQL connection from inside your xp? Then I suppose the same issues might apply that we were running into. But I still don't know what the workaround might be. To test if the encryption is actually causing the problem, you could see if forced data encryption is enabled on the development server. If it's not, you could enable it there, and see if that "breaks" your xp on the development server.
Other than that, I just wanted to mention that we'd seen a similar issue, but in reality, 17832 errors can be really hard to figure out. If you can test on the dev server, and your test disproves my theory, then maybe somebody else who has more experience debugging xp's can chime in. Otherwise ... and I hate to suggest this to 2 people on the same day ... but there are so few xp developers out there that maybe you should consider opening an incident with PSS.
Good luck,
Chris
-
well i guess, first you should find out what is causing the error, for that u have to use sqlserver profiler, and then make it to check on stored procedure, call ur stored procedure, and then look into the profiler for error messages,
u need to check logs in sql server for errors, u will find them and then search for solution for that error.
thats the only way
<a href="http://www.websolsoftware.com"> For IT jobs click here</a>
*Sukhoi*[font="Arial Narrow"][/font]
-
As what I posted, that is the only error message I can find. I think that the error is caused by the security context. It is so frustrating. Why can the client login to the server, but my "xp" cannot? The reason I can think of is Microsoft's DB-Library might be kind of outdated. Anyone has better ideas about how to handle my problems?
Thanks.
-
Does anyone have any ideas and experience about how to handle my problems?
-
did u tried what i said, did u use sql-profiler, it will give u better description for u r error
<a href="http://www.websolsoftware.com"> For IT jobs click here</a>
*Sukhoi*[font="Arial Narrow"][/font]
-
Maybe I do not make myself clear. The error I posted in my first message is the only detailed error log I can have from SQL server. The sql-profiler does not return any useful info for me. Or I might be miss something. Only thing I have from sql-profiler is Permissions(32), EventClass(Audit Object Permission Event) when I traced my xp procedure by it. Other than that, anything looks fine without any extra errors or warnings.
Does anyone have any experience upon that? thanks.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply