Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

sql 2000 jobs Expand / Collapse
Author
Message
Posted Friday, June 14, 2013 8:00 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:15 AM
Points: 314, Visits: 264
i have given access for a login to view sql jobs in sql 2000 server and the user is able to see the same whereas when he tries to connect from sql 2005 client(ssms). He is getting error like failed to retrieve data for this request.
Post #1463582
Posted Friday, June 14, 2013 8:07 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 3:11 PM
Points: 31,368, Visits: 15,837
It's not quite clear what you mean, or what you did for access.

What did you do to grant access.

When you say he gets an error, do you mean he connects to a SQL 2000 instance from SQL 2005's SSMS client?







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1463591
Posted Friday, June 14, 2013 8:14 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:15 AM
Points: 314, Visits: 264
I had given db owner , targetserverrole access to MSDB database so he is able to view the jobs when he tries to connect from enterprise manager(sql 2000 instance) but when the user tries to connect the same sql 2000 instance from sql 2005 client machine he gets an error.... Hope i explained
Post #1463594
Posted Friday, June 14, 2013 1:07 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 3:11 PM
Points: 31,368, Visits: 15,837
It still isn't quite clear. The exact error and exact steps are needed, but you can debug this yourself as well.

run a trace on the 2000 server and watch what is called when the user connects with Management Studio. It's possible there is still a permissions issues since SSMS might make a different call.

I haven't heard of this particular issue with SSMS connecting to 2000, but not many people try to give access to jobs.

The other option is to grant access to sysjobs and sysjobschedules and let the users access information through scripts.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1463749
Posted Sunday, June 16, 2013 10:05 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, December 4, 2014 7:54 PM
Points: 3,087, Visits: 2,686
premkuttan (6/14/2013)
I had given db owner , targetserverrole access to MSDB database so he is able to view the jobs when he tries to connect from enterprise manager(sql 2000 instance) but when the user tries to connect the same sql 2000 instance from sql 2005 client machine he gets an error.... Hope i explained


It's been a while since I used SQL 2000 but I think that the error when connecting to the SQL 2000 instance using SQL 2005 tools is because of changes that were introduced with SQL 2005. In particular, the object model used by Enterprise Manager is not supported when using Management Studio.



Post #1463982
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse