|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL 2005 Database Engine Tuning AdvisorMicrosoft Visual C++ Runtime Library Runtime Error! R6331 -Attempt to initialize the CRT more than once. This indicates a but in your application. The first step starts to run (Submitting Configuration Information), but it never moves on from there. I'm running sp1, and this behavior occurs on my desktop system, connected to a server. Running the process directly on the server does not produce this error. Can anyone assist with this? Thanks, Tom This is a known issue. Please see the following for details.
http://support.microsoft.com/?kbid=913395 I have copied the relevant information from the article here. If Database Engine Tuning Advisor inherits the application compatibility settings from the Explorer.exe process, the Microsoft Windows loader tries to initialize the C run-time library (CRT) Msvcp80.dll file two times when you start Database Engine Tuning Advisor. Therefore, Database Engine Tuning Advisor stops responding. Back to the top WORKAROUND Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. To work around this problem, you must set the Explorer.exe process to stop using the application compatibility technology. To do this, follow these steps:1. Click Start, click Run, type regedit, and then click OK. 2. Locate the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers 3. In the right pane, right-click the registry entry for the Explorer.exe process, and then click Delete. 4. In the Confirm Value Delete dialog box, click Yes. 5. Exit Registry Editor. 6. Restart the computer. Sanjay Sanjay,
Thanks very much for your reply. I looked for the key you mentioned, but there is no entry at all under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers. I did find it however in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers with a value EnableNXShowUI. I didn't do anything with it however, as the location does not correspond to your instructions, or the KB article's. Any suggestions? Show quote "sanja***@hotmail.com" wrote: > This is a known issue. Please see the following for details. > > http://support.microsoft.com/?kbid=913395 > > I have copied the relevant information from the article here. > > If Database Engine Tuning Advisor inherits the application > compatibility settings from the Explorer.exe process, the Microsoft > Windows loader tries to initialize the C run-time library (CRT) > Msvcp80.dll file two times when you start Database Engine Tuning > Advisor. Therefore, Database Engine Tuning Advisor stops responding. > Back to the top > > WORKAROUND > Warning Serious problems might occur if you modify the registry > incorrectly by using Registry Editor or by using another method. These > problems might require that you reinstall your operating system. > Microsoft cannot guarantee that these problems can be solved. Modify > the registry at your own risk. > > To work around this problem, you must set the Explorer.exe process to > stop using the application compatibility technology. To do this, follow > these steps:1. Click Start, click Run, type regedit, and then click OK. > > 2. Locate the following registry subkey: > HKEY_CURRENT_USER\Software\Microsoft\Windows > NT\CurrentVersion\AppCompatFlags\Layers > 3. In the right pane, right-click the registry entry for the > Explorer.exe process, and then click Delete. > 4. In the Confirm Value Delete dialog box, click Yes. > 5. Exit Registry Editor. > 6. Restart the computer. > > > Sanjay > > It's the same thing. I didn't have an entry in HKCU, but did have one in
HKLM. When I removed that key, DTA started working correctly. I really wish the install routine would detect that key and remove it. I've yet to find a machine that didn't have that key in the registry so that DTA would blow up on every single one of them and removing the key has zero effect on any applications. -- Show quoteMike http://www.solidqualitylearning.com Disclaimer: This communication is an original work and represents my sole views on the subject. It does not represent the views of any other person or entity either by inference or direct reference. "TomT" <tomt@newsgroup.nospam> wrote in message news:EC4BCC36-920E-4A5B-B04A-582F60A4E47C@microsoft.com... > Sanjay, > > Thanks very much for your reply. I looked for the key you mentioned, but > there is no entry at all under > HKEY_CURRENT_USER\Software\Microsoft\Windows > NT\CurrentVersion\AppCompatFlags\Layers. > > I did find it however in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows > NT\CurrentVersion\AppCompatFlags\Layers with a value EnableNXShowUI. I > didn't do anything with it however, as the location does not correspond to > your instructions, or the KB article's. > > Any suggestions? > > > > > "sanja***@hotmail.com" wrote: > >> This is a known issue. Please see the following for details. >> >> http://support.microsoft.com/?kbid=913395 >> >> I have copied the relevant information from the article here. >> >> If Database Engine Tuning Advisor inherits the application >> compatibility settings from the Explorer.exe process, the Microsoft >> Windows loader tries to initialize the C run-time library (CRT) >> Msvcp80.dll file two times when you start Database Engine Tuning >> Advisor. Therefore, Database Engine Tuning Advisor stops responding. >> Back to the top >> >> WORKAROUND >> Warning Serious problems might occur if you modify the registry >> incorrectly by using Registry Editor or by using another method. These >> problems might require that you reinstall your operating system. >> Microsoft cannot guarantee that these problems can be solved. Modify >> the registry at your own risk. >> >> To work around this problem, you must set the Explorer.exe process to >> stop using the application compatibility technology. To do this, follow >> these steps:1. Click Start, click Run, type regedit, and then click OK. >> >> 2. Locate the following registry subkey: >> HKEY_CURRENT_USER\Software\Microsoft\Windows >> NT\CurrentVersion\AppCompatFlags\Layers >> 3. In the right pane, right-click the registry entry for the >> Explorer.exe process, and then click Delete. >> 4. In the Confirm Value Delete dialog box, click Yes. >> 5. Exit Registry Editor. >> 6. Restart the computer. >> >> >> Sanjay >> >> Thanks for the reply. I did remove the entry in HKLM, but when I rebooted my
system I got a data execution error message re: explorer.exe. Then, when I checked the registry, the entry had been put back in..... I gather you removed it successfully - not sure why I can't. Show quote "Michael Hotek" wrote: > It's the same thing. I didn't have an entry in HKCU, but did have one in > HKLM. When I removed that key, DTA started working correctly. > > I really wish the install routine would detect that key and remove it. I've > yet to find a machine that didn't have that key in the registry so that DTA > would blow up on every single one of them and removing the key has zero > effect on any applications. > > -- > Mike > http://www.solidqualitylearning.com > Disclaimer: This communication is an original work and represents my sole > views on the subject. It does not represent the views of any other person > or entity either by inference or direct reference. > > > "TomT" <tomt@newsgroup.nospam> wrote in message > news:EC4BCC36-920E-4A5B-B04A-582F60A4E47C@microsoft.com... > > Sanjay, > > > > Thanks very much for your reply. I looked for the key you mentioned, but > > there is no entry at all under > > HKEY_CURRENT_USER\Software\Microsoft\Windows > > NT\CurrentVersion\AppCompatFlags\Layers. > > > > I did find it however in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows > > NT\CurrentVersion\AppCompatFlags\Layers with a value EnableNXShowUI. I > > didn't do anything with it however, as the location does not correspond to > > your instructions, or the KB article's. > > > > Any suggestions? > > > > > > > > > > "sanja***@hotmail.com" wrote: > > > >> This is a known issue. Please see the following for details. > >> > >> http://support.microsoft.com/?kbid=913395 > >> > >> I have copied the relevant information from the article here. > >> > >> If Database Engine Tuning Advisor inherits the application > >> compatibility settings from the Explorer.exe process, the Microsoft > >> Windows loader tries to initialize the C run-time library (CRT) > >> Msvcp80.dll file two times when you start Database Engine Tuning > >> Advisor. Therefore, Database Engine Tuning Advisor stops responding. > >> Back to the top > >> > >> WORKAROUND > >> Warning Serious problems might occur if you modify the registry > >> incorrectly by using Registry Editor or by using another method. These > >> problems might require that you reinstall your operating system. > >> Microsoft cannot guarantee that these problems can be solved. Modify > >> the registry at your own risk. > >> > >> To work around this problem, you must set the Explorer.exe process to > >> stop using the application compatibility technology. To do this, follow > >> these steps:1. Click Start, click Run, type regedit, and then click OK. > >> > >> 2. Locate the following registry subkey: > >> HKEY_CURRENT_USER\Software\Microsoft\Windows > >> NT\CurrentVersion\AppCompatFlags\Layers > >> 3. In the right pane, right-click the registry entry for the > >> Explorer.exe process, and then click Delete. > >> 4. In the Confirm Value Delete dialog box, click Yes. > >> 5. Exit Registry Editor. > >> 6. Restart the computer. > >> > >> > >> Sanjay > >> > >> > > > Hello,
Please check if an environment variable __COMPAT_LAYER is set? You may wawnt to run the following command in CMD: "set __COMPAT_LAYER=" It seems the registry key is added by some programs on the machine automatically. You may want to check if the issue occur under the following situation: 1. Run the System Configuration Utility (msconfig.exe): Click Start->Run, type "msconfig"(without quotation mark) in the open box, and click OK. 2. On the General tab, select "Selective Startup" and then deselect Load Startup items, select the checks on other options. 3. On the Services tab, click Hide All Microsoft Services. Deselect all the items left. 4. Click the Apply button. 5. Delete the value Explorer.exe HKLM\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers 5. Reboot your computer to check if the issue still occurs. Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights.  |
|||||||||||||||||||||||
Other interesting topics