Viewing 14 posts - 1,321 through 1,334 (of 1,334 total)
Please check for the registry privileges in that particular machine for that particular user i hope so the windows account does not have registry access that's why you get a...
January 7, 2007 at 6:14 am
just check in your backup jobs for any schedules that are scheduled to occur monthly and 30th of every month by this you can find what is running concurrently.
January 5, 2007 at 6:54 am
ask the user to logoff and then login and access the sql server.
January 5, 2007 at 6:40 am
whats the size of the database. check your event viewer for any errors in the disk also check for the error log and let us know whats the exact error...
January 5, 2007 at 4:30 am
try using locking hints in your update statement so that it locks only for updates and allows select.
January 5, 2007 at 12:54 am
Thi solution will surely work for you just try this.
1. Give the users the necessary permissions
2. create a DSN in thier machine with proper database access
3. ask the user...
January 4, 2007 at 6:54 am
I hope the script in this link http://www.sqlservercentral.com/scripts/contributions/1598.asp will solve your issue.
January 4, 2007 at 6:27 am
Just check this link. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=904828&SiteID=1
Also i would like to know ur parameters that you are using in creating the linked server.
January 4, 2007 at 6:22 am
The same tables are used in sql 2005 also. you can query those tables to find the necessary details
January 4, 2007 at 6:09 am
script out your sql server login with the object level permissions and use that script to create your new login
January 3, 2007 at 6:48 am
just try accessing your access database with opendatasource to see if you get the error in that also if so please send the exact error message
January 3, 2007 at 6:42 am
where is your query outputting too. check f ur sql server has permission to write to that path. it must be a permission problem with windows file and folder. check...
December 13, 2006 at 12:29 am
whats the amount of RAM in your server. Also check if your server has query timed out option enabled. check SET LOCK_TIMEOUT parameter also.
November 28, 2006 at 5:36 am
Hi all
I have solved this problem. The problem was not with SQL Server but was with WINDOWS 2003 DISTRIBUTED TRANSACTION CO-ORDINATOR. It was set to required password more and...
October 17, 2006 at 8:26 am
Viewing 14 posts - 1,321 through 1,334 (of 1,334 total)