Weird Resource Database Message in Error Log

Question

Weird Resource Database Message in Error Log

PhilipC

Hall of Fame

Points: 3124
More actions
February 6, 2012 at 9:06 pm

#251034

I'm getting this message in the error-log each time on a SQL restart.
The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.INSTANCENAME\MSSQL\Binn\sqlservr.exe' instead of the currently attached resource database at 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.INSTANCENAME\MSSQL\Binn\mssqlsystemresource.mdf'.
Anyone struck this before and know what it's about? The path is the same for both :blink:

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

sumitagarwal781 Default port Points: 1493 More actions · Answer 1

it seems you moved the resourceDB to other location. after restart it will show both location in error log. next time it wont trigger the same error.

java

PhilipC Hall of Fame Points: 3124 More actions · Answer 2

I've had this for a number of months now, each time the instance is restarted, receive this message.

mvishnu7 SSC Journeyman Points: 97 More actions · Answer 3

hi

After Attaching the resource database in the same directory .restart the server and remove the file prevoius location,where it is pointing out.

PhilipC Hall of Fame Points: 3124 More actions · Answer 4

PhilipC

Hall of Fame

Points: 3124

February 7, 2012 at 1:00 am

#1443567

Hi there, but it's the same location?

ft55 Ten Centuries Points: 1210 More actions · Answer 5

Hi,

Did you get a fix for this issue ? we are seeing this on our instances after adding a node to a cluster. It doesnt really make much sense as the paths are the same :

Message

The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DB0\MSSQL\Binn\sqlservr.exe' instead of the currently attached resource database at 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.DB0\MSSQL\Binn\mssqlsystemresource.mdf'.

Thanks

PhilipC Hall of Fame Points: 3124 More actions · Answer 6

Sorry ft55 I don't remember what we did. If it comes to mind over the next few days, I'll post back.

ingcruzmoreno SSC Rookie Points: 47 More actions · Answer 7

Were you able to fix this problem? I just got the same error. :S

drew.allen SSC Guru Points: 76997 More actions · Answer 8

ingcruzmoreno (12/6/2016)
Were you able to fix this problem? I just got the same error. :S

He already said that he had fixed it, but didn't remember what he did. And that was three years ago, so it's even less likely that he remembers now.

Drew

J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA

ft55 Ten Centuries Points: 1210 More actions · Answer 9

I can't remember the exact details but our issues were all down to case sensitivity :

Message

The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.DB0\MSSQL\Binn\sqlservr.exe' instead of the currently attached resource database at 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.DB0\MSSQL\Binn\mssqlsystemresource.mdf'.

Note that the first path use a C:\ and the second path uses a c:

We had to change a regkey to get this working i'll see if I documented it anywhere.....

thierry.vandurme Hall of Fame Points: 3340 More actions · Answer 10

It's indeed due to the different capitalization ( c: vs C: ).
You need to change it in the registry where the service configuration is kept: HKLM\SYSTEM\CurrentControlSet\Services. Find your instance and look at the ImagePath key. It'll have either a small c: or capital C:.
It's a bit strange that you receive this message at every restart because once SQL starts it records the "correct" value in sysaltfiles and it shouldn't complain at the next restart. At least that's what I saw while testing.
Hope this helps

thierry.vandurme Hall of Fame Points: 3340 More actions · Answer 11

thierry.vandurme - Monday, February 20, 2017 8:29 AM
It's indeed due to the different capitalization ( c: vs C: ).
You need to change it in the registry where the service configuration is kept: HKLM\SYSTEM\CurrentControlSet\Services. Find your instance and look at the ImagePath key. It'll have either a small c: or capital C:.
It's a bit strange that you receive this message at every restart because once SQL starts it records the "correct" value in sysaltfiles and it shouldn't complain at the next restart. At least that's what I saw while testing.
Hope this helps

Just figured out why it could give you that message more than once. If you have a cluster the nodes may have different values. If they failover/back you'll see the message again. So you need to change all the nodes in your cluster