Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
zaty2405
Yak Posting Veteran
58 Posts |
 Posted - 2010-02-28 : 04:27:29
|
| Hi ,Users were not able to access the production server for an hour.During the 1 hour duration the following error keep on appearing in :sql log file :- login failed for user ' null '. reason not associated with a trusted sql server connectionEvent Viewer:-SQL Server Scheduled Job '1234_hdfgdf' (0xEC7A3765BB1BF64DAA62BA8027231C77) - Status: Failed - Invoked on: 2010-02-27 18:32:04 - Message: The job failed. Unable to determine if the owner (Europe\SQL-RNM123-I01-S) of job 1234_hdfgdf has server access (reason: Could not obtain information about Windows NT group/user 'Europe\SQL-RNM123-I01-S'. [SQLSTATE 42000] (Error 8198)).How to find what caused this and how to resolve it.Thanks |
|
|
zaty2405
Yak Posting Veteran
58 Posts |
Posted - 2010-02-28 : 06:14:45
|
| hi,1) Is this a network issue?2) Can this caused by a few minutes time different between database server and web server? |
 |
|
|
sathiesh2005
Yak Posting Veteran
85 Posts |
Posted - 2010-03-04 : 01:53:35
|
| hI,Did you restored your database or some other database in the same server recently?I had the same problem few months before when i restored a particular database.now it was ok. Reason for my problem is that i have linked my DB to other DB with readonly permission. When i restored the linked DB, my DB thrown the error login failed for user '',Solution:I looked at the users at each database(at Enterprise manager) my DB user was set to null at the time of restoring the DB. I entered the login name there. My problem solved.Is your problem solved? If so post the solution.Regards,Sathieshkumar. R |
|
|
|
thewebhosting
Starting Member
17 Posts |
Posted - 2010-03-24 : 18:02:29
|
| Hi,Check with these options:- Reset the details ion server and reflect it in the connection string.- Make sure that you have used correct port to connect to your SQL web server. If you do not have any details of it then you can contact your service provider and get the details. Generally, MS SQL is running on 1533 port.- Make sure that MS SQL web server is not down.- If require then increase connection timeout limit either from the code from the server. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-03-25 : 04:49:06
|
| I reckon that the database became full and was extended. This is a particularly slow operation under SQL 2000 if:1) The database is set to increase by PERCENTAGE (rather than FIXED amount) and the percentage increase is large - say 1GB2) The database is heavily used. Lots of people sending queries (which would all timeout, which will cause people to retry, which will make the problem worse)If this is the case then set the Expansion to a modest Fixed Amount - enough for at least a week, but preferably only 50MB or maybe 100MB (but it depends on how fast your hardware is) |
|
|
|
|
|
|
|
|
User not able to access database