MS SQL Server - Tuning Advisor Crashing in SQL Server 2005

Author

Tuning Advisor Crashing in SQL Server 2005

Sinan

2005-12-06, 3:23 am

Hi,

I am using SQL Server 2005
The issue is with database engine tuning advisor. Below is my version:

9.00.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00
(xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
--------------------------

When click connect in the tuning advisor, I get this run time error: R6031
(attempt to initialize the CRT more than once).

Any ideas?

Thanks,
S.

Michael Carr

2005-12-07, 1:23 pm

I am having the exact same problem. No idea how to fix it...

Michael Carr

"Sinan" <Sinan@discussions.microsoft.com> wrote in message
news:BCBDB4C7-E98E-4A24-9A76- 2ADFC8F966CE@microso
ft.com...
> When click connect in the tuning advisor, I get this run time error: R6031
> (attempt to initialize the CRT more than once).

ap.marathe@gmail.com

2005-12-10, 3:23 am

We have obtained a repro for this error in-house, and a DTA developer
is looking at it. Based on his investigation, we will decide on the
next steps.

Thanks,
Arun Marathe
DTA Program Manager

Chris

2005-12-14, 8:23 pm

I'm experiencing the same problem, fwiw. Just added a post to a similar
thread ("Re: Error using Db Engine Tuning Advisor") on
microsoft.public.sqlserver.tools.

<ap.marathe@gmail.com> wrote in message
news:1134183354.958591.256700@g44g2000cwa.googlegroups.com...
>
> We have obtained a repro for this error in-house, and a DTA developer
> is looking at it. Based on his investigation, we will decide on the
> next steps.
>
> Thanks,
> Arun Marathe
> DTA Program Manager
>

Chris

2005-12-21, 11:23 am

Anything new to report on this? It's been almost two weeks since your last
posting.

<ap.marathe@gmail.com> wrote in message
news:1134183354.958591.256700@g44g2000cwa.googlegroups.com...
>
> We have obtained a repro for this error in-house, and a DTA developer
> is looking at it. Based on his investigation, we will decide on the
> next steps.
>
> Thanks,
> Arun Marathe
> DTA Program Manager
>

manojas@hotmail.com

2005-12-29, 8:23 pm

This issue is being investigated presently and is probably a
consequence of a filed windows/appcompat bug
(issue due to appcompat shimming and nothing to do with DTA process
itself -).

1.Can you check if you have registry entries corresponding to
HKLM\Software\Micros
oft\Windows
NT\CurrentVersion\Ap
pCompatFlags\Layers?
In the past we have seen "explorer.exe " as an entry and removing that
fixed the problem

2.Also please check if an environment variable __COMPAT_LAYER is set?
"set __COMPAT_LAYER=" , basically disabled the compat layer and dta
ran OK

Please note that none of these are set by the tuning advisor exe - At
this point i am not sure what app does this

Manoj

manojas@hotmail.com

2006-01-03, 8:23 pm

We have identified this to be a problem caused by AppCompat layer in
Windows OS.

In short this technology allows older applications to run on newer
Windows OS by simulating parts of older Windows API. This is done by
injecting special "shims" into an application process. This technology
can be turned on and off on per process basis.

There are two issues that cause the problem in DTA process.

1) First, on some machines the explorer.exe process is marked to use
some AppCompat shims. This should not be done in general, since this
causes all applications started from this process to inherit the same
AppCompat settings. Most of user-launched applications are started from
explorer.exe process.

2) Second, there is a defect in AppCompat layer that causes double
initialization of CRT libraries and results in process termination. The
defect has already been logged.

Before the defect is fixed and fix released in a future service pack,
the solution to this problem is to remove AppCompat settings from the
explorer.exe process.

Workaround

Start the regedit tool and navigate to the following registry key:

HKLM\Software\Micros
oft\Windows
NT\CurrentVersion\Ap
pCompatFlags\Layers

and locate an entry for explorer.exe. Then delete it. For that to take
effect you need to either restart the system or kill explorer.exe
process and start it again.

As usual, when changing content of the registry it is advised to make a
backup copy of modified keys before doing any changes.

We will be working on a KB article to describe this issue.

manojas@hotmail.com wrote:
> This issue is being investigated presently and is probably a
> consequence of a filed windows/appcompat bug
> (issue due to appcompat shimming and nothing to do with DTA process
> itself -).
>
> 1.Can you check if you have registry entries corresponding to
> HKLM\Software\Micros
oft\Windows
> NT\CurrentVersion\Ap
pCompatFlags\Layers?
> In the past we have seen "explorer.exe " as an entry and removing that
> fixed the problem
>
> 2.Also please check if an environment variable __COMPAT_LAYER is set?
> "set __COMPAT_LAYER=" , basically disabled the compat layer and dta
> ran OK
>
> Please note that none of these are set by the tuning advisor exe - At
> this point i am not sure what app does this
>
> Manoj

Sponsored Links