Problem with Extended Stored Procedure calling an WebService...

Hi all!
I have a problem with a Extended Stored Procedure that calls a
WebService...I'm using SOAP to call the WebService and I'm using an
TokenManager that I have written myself...I have WSE 2.0 installed...
It works fine when I'm calling it from my PC, but when I call it from the
SQL test server which is a Windows 2003 server with SQL Server 2000
installed.
The message we get when run the Extended Stored Procedure is.
ODBC: Msg 0, Level 16, State 1
Cannot load the DLL XpMQSQL.DLL, or one of the DLLs it references. Reason:
126(The specified module could not be found.).
Does anyone know what I'm missing? We tried to install WSE 2.0 runtime
version but that didn't help...
Regards,
Tommy Selggren
Mandator Sverige AB
http://www.mandator.comUse DEPENDS.EXE to figure out which file(s) is/are missing. Download
DEPENS.EXE from http://www.dependencywalker.com/ and point it at you DLL
which hosts the XP
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Tommy Selggren" <tommy.selggren@.telia.com> wrote in message
news:e$pRK3kGFHA.2136@.TK2MSFTNGP14.phx.gbl...
> Hi all!
> I have a problem with a Extended Stored Procedure that calls a
> WebService...I'm using SOAP to call the WebService and I'm using an
> TokenManager that I have written myself...I have WSE 2.0 installed...
> It works fine when I'm calling it from my PC, but when I call it from the
> SQL test server which is a Windows 2003 server with SQL Server 2000
> installed.
> The message we get when run the Extended Stored Procedure is.
> ODBC: Msg 0, Level 16, State 1
> Cannot load the DLL XpMQSQL.DLL, or one of the DLLs it references. Reason:
> 126(The specified module could not be found.).
> Does anyone know what I'm missing? We tried to install WSE 2.0 runtime
> version but that didn't help...
> Regards,
> Tommy Selggren
> Mandator Sverige AB
> http://www.mandator.com
>
>|||Many thanks!
"Gert E.R. Drapers" <GertD@.SQLDevNet> wrote in message
news:eT2QgflGFHA.3092@.tk2msftngp13.phx.gbl...
> Use DEPENDS.EXE to figure out which file(s) is/are missing. Download
> DEPENS.EXE from http://www.dependencywalker.com/ and point it at you DLL
> which hosts the XP
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2005 All rights reserved.
> "Tommy Selggren" <tommy.selggren@.telia.com> wrote in message
> news:e$pRK3kGFHA.2136@.TK2MSFTNGP14.phx.gbl...
the
Reason:
>

Problem with extended procedure

Hi all,
i have MS SQL Server 2000 Standard with my own extended procedure. I run
extended procedurec, and this procedure make sepparate session and run stored
procedure (asynchronous). But the extended procedure failed with error:
Server user 'domain\xxx' is not a valid user in database 'db'.
Database 'db' was restore from backup from another server, but user's SID is
the same as login, there is no orphanes , or somethink like that. (to be on
the safe said)I drop the user and the login and create new login and user .
But no change.
User domain\xxx is the local admin, and MS SQL Server and ServerAgent start
with this account.
Any suggestion?
Thanks Honza
Run the query below to verify the login is a sysadmin role member. Also,
verify that you are connecting to the correct SQL Server instance from your
extended proc. A Profiler trace may help.
SELECT IS_SRVROLEMEMBER ('sysadmin' , 'domain\xxx')
Hope this helps.
Dan Guzman
SQL Server MVP
"Jan Schustr" <Jan Schustr@.discussions.microsoft.com> wrote in message
news:10A5175F-50C8-4C0E-B503-47CD5B08D4C5@.microsoft.com...
> Hi all,
> i have MS SQL Server 2000 Standard with my own extended procedure. I run
> extended procedurec, and this procedure make sepparate session and run
> stored
> procedure (asynchronous). But the extended procedure failed with error:
> Server user 'domain\xxx' is not a valid user in database 'db'.
> Database 'db' was restore from backup from another server, but user's SID
> is
> the same as login, there is no orphanes , or somethink like that. (to be
> on
> the safe said)I drop the user and the login and create new login and user
> .
> But no change.
> User domain\xxx is the local admin, and MS SQL Server and ServerAgent
> start
> with this account.
> Any suggestion?
> Thanks Honza

Problem with extended procedure

Hi all,
i have MS SQL Server 2000 Standard with my own extended procedure. I run
extended procedurec, and this procedure make sepparate session and run stored
procedure (asynchronous). But the extended procedure failed with error:
Server user 'domain\xxx' is not a valid user in database 'db'.
Database 'db' was restore from backup from another server, but user's SID is
the same as login, there is no orphanes , or somethink like that. (to be on
the safe said)I drop the user and the login and create new login and user .
But no change.
User domain\xxx is the local admin, and MS SQL Server and ServerAgent start
with this account.
Any suggestion?
Thanks HonzaRun the query below to verify the login is a sysadmin role member. Also,
verify that you are connecting to the correct SQL Server instance from your
extended proc. A Profiler trace may help.
SELECT IS_SRVROLEMEMBER ('sysadmin' , 'domain\xxx')
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Jan Schustr" <Jan Schustr@.discussions.microsoft.com> wrote in message
news:10A5175F-50C8-4C0E-B503-47CD5B08D4C5@.microsoft.com...
> Hi all,
> i have MS SQL Server 2000 Standard with my own extended procedure. I run
> extended procedurec, and this procedure make sepparate session and run
> stored
> procedure (asynchronous). But the extended procedure failed with error:
> Server user 'domain\xxx' is not a valid user in database 'db'.
> Database 'db' was restore from backup from another server, but user's SID
> is
> the same as login, there is no orphanes , or somethink like that. (to be
> on
> the safe said)I drop the user and the login and create new login and user
> .
> But no change.
> User domain\xxx is the local admin, and MS SQL Server and ServerAgent
> start
> with this account.
> Any suggestion?
> Thanks Honza

Problem with extended procedure

Hi all,
i have MS SQL Server 2000 Standard with my own extended procedure. I run
extended procedurec, and this procedure make sepparate session and run store
d
procedure (asynchronous). But the extended procedure failed with error:
Server user 'domain\xxx' is not a valid user in database 'db'.
Database 'db' was restore from backup from another server, but user's SID is
the same as login, there is no orphanes , or somethink like that. (to be on
the safe said)I drop the user and the login and create new login and user .
But no change.
User domain\xxx is the local admin, and MS SQL Server and ServerAgent start
with this account.
Any suggestion?
Thanks HonzaRun the query below to verify the login is a sysadmin role member. Also,
verify that you are connecting to the correct SQL Server instance from your
extended proc. A Profiler trace may help.
SELECT IS_SRVROLEMEMBER ('sysadmin' , 'domain\xxx')
Hope this helps.
Dan Guzman
SQL Server MVP
"Jan Schustr" <Jan Schustr@.discussions.microsoft.com> wrote in message
news:10A5175F-50C8-4C0E-B503-47CD5B08D4C5@.microsoft.com...
> Hi all,
> i have MS SQL Server 2000 Standard with my own extended procedure. I run
> extended procedurec, and this procedure make sepparate session and run
> stored
> procedure (asynchronous). But the extended procedure failed with error:
> Server user 'domain\xxx' is not a valid user in database 'db'.
> Database 'db' was restore from backup from another server, but user's SID
> is
> the same as login, there is no orphanes , or somethink like that. (to be
> on
> the safe said)I drop the user and the login and create new login and user
> .
> But no change.
> User domain\xxx is the local admin, and MS SQL Server and ServerAgent
> start
> with this account.
> Any suggestion?
> Thanks Honza