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
Showing posts with label session. Show all posts
Showing posts with label session. Show all posts
Monday, March 12, 2012
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
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
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
Saturday, February 25, 2012
problem with default path for osql
Hi!
I have a following problem:
When I run osql from cmd prompt it is running fine, however if I have to run
osql from another osql session by using xp_cmdshell 'osql ...'. It can not
find the osql file.
I 've checked both PATH variable as well as registry
HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetu p\SqlPath are set to proper
value. What is missing
I've seen this on machines that didn't reboot since installation. I worked around it by checking
registry entries for SQL server and build the bath based on that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"kimi" <kimi@.discussions.microsoft.com> wrote in message
news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> Hi!
> I have a following problem:
> When I run osql from cmd prompt it is running fine, however if I have to run
> osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> find the osql file.
> I 've checked both PATH variable as well as registry
> HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetu p\SqlPath are set to proper
> value. What is missing
|||Are you suggesting that I should hardcode path to osql if reboot does not help?
"Tibor Karaszi" wrote:
> I've seen this on machines that didn't reboot since installation. I worked around it by checking
> registry entries for SQL server and build the bath based on that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "kimi" <kimi@.discussions.microsoft.com> wrote in message
> news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
>
|||Reboot did not help. Any ideas?
"kimi" wrote:
[vbcol=seagreen]
> Are you suggesting that I should hardcode path to osql if reboot does not help?
> "Tibor Karaszi" wrote:
I have a following problem:
When I run osql from cmd prompt it is running fine, however if I have to run
osql from another osql session by using xp_cmdshell 'osql ...'. It can not
find the osql file.
I 've checked both PATH variable as well as registry
HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetu p\SqlPath are set to proper
value. What is missing
I've seen this on machines that didn't reboot since installation. I worked around it by checking
registry entries for SQL server and build the bath based on that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"kimi" <kimi@.discussions.microsoft.com> wrote in message
news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> Hi!
> I have a following problem:
> When I run osql from cmd prompt it is running fine, however if I have to run
> osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> find the osql file.
> I 've checked both PATH variable as well as registry
> HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetu p\SqlPath are set to proper
> value. What is missing
|||Are you suggesting that I should hardcode path to osql if reboot does not help?
"Tibor Karaszi" wrote:
> I've seen this on machines that didn't reboot since installation. I worked around it by checking
> registry entries for SQL server and build the bath based on that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "kimi" <kimi@.discussions.microsoft.com> wrote in message
> news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
>
|||Reboot did not help. Any ideas?
"kimi" wrote:
[vbcol=seagreen]
> Are you suggesting that I should hardcode path to osql if reboot does not help?
> "Tibor Karaszi" wrote:
problem with default path for osql
Hi!
I have a following problem:
When I run osql from cmd prompt it is running fine, however if I have to run
osql from another osql session by using xp_cmdshell 'osql ...'. It can not
find the osql file.
I 've checked both PATH variable as well as registry
HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
value. What is missingI've seen this on machines that didn't reboot since installation. I worked around it by checking
registry entries for SQL server and build the bath based on that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"kimi" <kimi@.discussions.microsoft.com> wrote in message
news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> Hi!
> I have a following problem:
> When I run osql from cmd prompt it is running fine, however if I have to run
> osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> find the osql file.
> I 've checked both PATH variable as well as registry
> HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
> value. What is missing|||Are you suggesting that I should hardcode path to osql if reboot does not help?
"Tibor Karaszi" wrote:
> I've seen this on machines that didn't reboot since installation. I worked around it by checking
> registry entries for SQL server and build the bath based on that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "kimi" <kimi@.discussions.microsoft.com> wrote in message
> news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> > Hi!
> > I have a following problem:
> > When I run osql from cmd prompt it is running fine, however if I have to run
> > osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> > find the osql file.
> > I 've checked both PATH variable as well as registry
> > HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
> > value. What is missing
>|||Reboot did not help. Any ideas?
"kimi" wrote:
> Are you suggesting that I should hardcode path to osql if reboot does not help?
> "Tibor Karaszi" wrote:
> > I've seen this on machines that didn't reboot since installation. I worked around it by checking
> > registry entries for SQL server and build the bath based on that.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> > Blog: http://solidqualitylearning.com/blogs/tibor/
> >
> >
> > "kimi" <kimi@.discussions.microsoft.com> wrote in message
> > news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> > > Hi!
> > > I have a following problem:
> > > When I run osql from cmd prompt it is running fine, however if I have to run
> > > osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> > > find the osql file.
> > > I 've checked both PATH variable as well as registry
> > > HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
> > > value. What is missing
> >
> >
I have a following problem:
When I run osql from cmd prompt it is running fine, however if I have to run
osql from another osql session by using xp_cmdshell 'osql ...'. It can not
find the osql file.
I 've checked both PATH variable as well as registry
HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
value. What is missingI've seen this on machines that didn't reboot since installation. I worked around it by checking
registry entries for SQL server and build the bath based on that.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"kimi" <kimi@.discussions.microsoft.com> wrote in message
news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> Hi!
> I have a following problem:
> When I run osql from cmd prompt it is running fine, however if I have to run
> osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> find the osql file.
> I 've checked both PATH variable as well as registry
> HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
> value. What is missing|||Are you suggesting that I should hardcode path to osql if reboot does not help?
"Tibor Karaszi" wrote:
> I've seen this on machines that didn't reboot since installation. I worked around it by checking
> registry entries for SQL server and build the bath based on that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "kimi" <kimi@.discussions.microsoft.com> wrote in message
> news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> > Hi!
> > I have a following problem:
> > When I run osql from cmd prompt it is running fine, however if I have to run
> > osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> > find the osql file.
> > I 've checked both PATH variable as well as registry
> > HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
> > value. What is missing
>|||Reboot did not help. Any ideas?
"kimi" wrote:
> Are you suggesting that I should hardcode path to osql if reboot does not help?
> "Tibor Karaszi" wrote:
> > I've seen this on machines that didn't reboot since installation. I worked around it by checking
> > registry entries for SQL server and build the bath based on that.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> > Blog: http://solidqualitylearning.com/blogs/tibor/
> >
> >
> > "kimi" <kimi@.discussions.microsoft.com> wrote in message
> > news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> > > Hi!
> > > I have a following problem:
> > > When I run osql from cmd prompt it is running fine, however if I have to run
> > > osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> > > find the osql file.
> > > I 've checked both PATH variable as well as registry
> > > HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to proper
> > > value. What is missing
> >
> >
problem with default path for osql
Hi!
I have a following problem:
When I run osql from cmd prompt it is running fine, however if I have to run
osql from another osql session by using xp_cmdshell 'osql ...'. It can not
find the osql file.
I 've checked both PATH variable as well as registry
HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to prope
r
value. What is missingI've seen this on machines that didn't reboot since installation. I worked a
round it by checking
registry entries for SQL server and build the bath based on that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"kimi" <kimi@.discussions.microsoft.com> wrote in message
news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> Hi!
> I have a following problem:
> When I run osql from cmd prompt it is running fine, however if I have to r
un
> osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> find the osql file.
> I 've checked both PATH variable as well as registry
> HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to pro
per
> value. What is missing|||Are you suggesting that I should hardcode path to osql if reboot does not he
lp?
"Tibor Karaszi" wrote:
> I've seen this on machines that didn't reboot since installation. I worked
around it by checking
> registry entries for SQL server and build the bath based on that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "kimi" <kimi@.discussions.microsoft.com> wrote in message
> news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
>|||Reboot did not help. Any ideas?
"kimi" wrote:
[vbcol=seagreen]
> Are you suggesting that I should hardcode path to osql if reboot does not
help?
> "Tibor Karaszi" wrote:
>
I have a following problem:
When I run osql from cmd prompt it is running fine, however if I have to run
osql from another osql session by using xp_cmdshell 'osql ...'. It can not
find the osql file.
I 've checked both PATH variable as well as registry
HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to prope
r
value. What is missingI've seen this on machines that didn't reboot since installation. I worked a
round it by checking
registry entries for SQL server and build the bath based on that.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"kimi" <kimi@.discussions.microsoft.com> wrote in message
news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
> Hi!
> I have a following problem:
> When I run osql from cmd prompt it is running fine, however if I have to r
un
> osql from another osql session by using xp_cmdshell 'osql ...'. It can not
> find the osql file.
> I 've checked both PATH variable as well as registry
> HKEY_LOCAL_MACHINE\Software...\80\Tools\ClientSetup\SqlPath are set to pro
per
> value. What is missing|||Are you suggesting that I should hardcode path to osql if reboot does not he
lp?
"Tibor Karaszi" wrote:
> I've seen this on machines that didn't reboot since installation. I worked
around it by checking
> registry entries for SQL server and build the bath based on that.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "kimi" <kimi@.discussions.microsoft.com> wrote in message
> news:84B0A2D8-17CA-449A-A012-B939B672465A@.microsoft.com...
>|||Reboot did not help. Any ideas?
"kimi" wrote:
[vbcol=seagreen]
> Are you suggesting that I should hardcode path to osql if reboot does not
help?
> "Tibor Karaszi" wrote:
>
Subscribe to:
Posts (Atom)