Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a web application that runs fine in our loadtest and dev environments, but runs very slow in our production environment. Using procexp64.exe from sysinternals I found threads that reference StrongNameError. This only occurs on our production servers and does not occur on our loadtest or dev servers. The web application on each set of servers is identical (I'm confirmed this multiple times as I'm struggling to resolve this error.

Example Thread: mscorwks.dll!StrongNameErrorInfo+0x7638

IIS is configured the same on all servers. The only difference I have been able to discover is the version of Windows. Oddly enough, our loadtest and dev servers are running enterprise and our production servers are running standard.

Is there some little known different between Windows 2008 Standard and Windows 2008 Enterprise that would shed light on this error and possible resolution?

share|improve this question
    
@Brian: 2 questions: are both servers the same architecture (both 32-bit or both 64-bit)? and do you have symbols properly configured for process explorer? –  MattB Nov 11 '10 at 20:12
    
Yes both servers are 64 bit. –  Brian Nov 11 '10 at 21:00
    
I believe the symbols are properly configured. At first I didn't have all the required sysmbols, but downloaded and installed those missing. I'll do a file comparison now to ensure C:\windows\symbols match on both servers. –  Brian Nov 11 '10 at 21:03
    
I confirmed the correct symbols are infact installed on the production server. A comparison of the symbols of the two servers would not be helpful as the production server is on SP2 and the dev sever is on sp1. If I read this page microsoft.com/whdc/devtools/debugging/symbolpkg.mspx correctly, the symbols are different based on service pack level. Still stumped. –  Brian Nov 11 '10 at 21:42
    
@Brian: going from SP1 (I assume you mean RTM since there is no 2008 SP1) to SP2 is a much bigger difference than going from Standard to Enterprise, and should probably be noted in your question. Are you positive that the same version of the .Net framework is registered for your IIS site? I don't know how up to date you keep your systems, but 2008 shipped with .Net 2.0 SP1, and 2008SP2 shipped .Net 2.0 SP2. You can of course upgrade them to the same level. –  MattB Nov 12 '10 at 22:04

1 Answer 1

I am struggling with a very similar problem. My threads are sitting in clr.dll!StrongNameErrorInfo. I managed to find this post, which suggests that Process Explorer can be wrong about what method the threads are in.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.