|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Error using Db Engine Tuning AdvisorI am running SQL 2005 Standard, obtained from a recent Launch event.
I got the Database Engine Tuning Advisor to run only once. Everytime after that I get a runtime error: "R6031 Attempt to initialize the CRT more than once. This indicates a bug in your application." I had the same problem with the Sept. CTP release. Re-booting the machine does not solve this problem. Basicaly, this is a useless tool if I need to un-install and re-install it everytime I need to use it. I have tried deleting all the sessions and creating a new one, re-booting. Any ideas how to solve this? Do I need to wait for a Service Pack? We are looking at the issue currently. It has been reported by a few other
people. Please gi ve us some more detail: - does this happen immiediately after you start DTA UI or after you connect to the server and the connection dialog goes away? - if this is the second case (error after connecting) does the problem occur if you simply Cancel the connection dialog? - have you tried command-line DTA to see if it work? Run 'dta.exe /?' to see the options if you have not seen it yet. - does the error message contain any more information? - can you check if at the time you see the error there is a dtaengine90.exe process running on your system? Thanks, Maciek Show quote "Todd C" <To***@discussions.microsoft.com> wrote in message news:438AAABC-1BA2-4677-B272-5D7766BEF9E2@microsoft.com... >I am running SQL 2005 Standard, obtained from a recent Launch event. > > I got the Database Engine Tuning Advisor to run only once. Everytime after > that I get a runtime error: "R6031 Attempt to initialize the CRT more than > once. This indicates a bug in your application." > > I had the same problem with the Sept. CTP release. Re-booting the machine > does not solve this problem. Basicaly, this is a useless tool if I need to > un-install and re-install it everytime I need to use it. I have tried > deleting all the sessions and creating a new one, re-booting. > > Any ideas how to solve this? Do I need to wait for a Service Pack? Is this TechNet discussion forum the best place to correspond regarding tech
support and error information? I would be happy to supply any information you need. Can you e-mail me a valid address so that we can take this 'off-line'? Thank you. todd_dot_chittenden_at_morantug_dot_com Show quote "Maciek Sarnowicz [MSFT]" wrote: > We are looking at the issue currently. It has been reported by a few other > people. Please gi ve us some more detail: > > - does this happen immiediately after you start DTA UI or after you connect > to the server and the connection dialog goes away? > - if this is the second case (error after connecting) does the problem occur > if you simply Cancel the connection dialog? > - have you tried command-line DTA to see if it work? Run 'dta.exe /?' to see > the options if you have not seen it yet. > - does the error message contain any more information? > - can you check if at the time you see the error there is a dtaengine90.exe > process running on your system? > > Thanks, > Maciek > > > "Todd C" <To***@discussions.microsoft.com> wrote in message > news:438AAABC-1BA2-4677-B272-5D7766BEF9E2@microsoft.com... > >I am running SQL 2005 Standard, obtained from a recent Launch event. > > > > I got the Database Engine Tuning Advisor to run only once. Everytime after > > that I get a runtime error: "R6031 Attempt to initialize the CRT more than > > once. This indicates a bug in your application." > > > > I had the same problem with the Sept. CTP release. Re-booting the machine > > does not solve this problem. Basicaly, this is a useless tool if I need to > > un-install and re-install it everytime I need to use it. I have tried > > deleting all the sessions and creating a new one, re-booting. > > > > Any ideas how to solve this? Do I need to wait for a Service Pack? > > > I will take this off-line as Todd requested. We will post back to the group
once we know the root cause of the issue. Thanks, Maciek Show quote "Todd C" <To***@discussions.microsoft.com> wrote in message news:F4881BF8-E66B-403B-9DA0-1BC4020DDF7F@microsoft.com... > Is this TechNet discussion forum the best place to correspond regarding > tech > support and error information? > > I would be happy to supply any information you need. Can you e-mail me a > valid address so that we can take this 'off-line'? > > Thank you. > > todd_dot_chittenden_at_morantug_dot_com > > "Maciek Sarnowicz [MSFT]" wrote: > >> We are looking at the issue currently. It has been reported by a few >> other >> people. Please gi ve us some more detail: >> >> - does this happen immiediately after you start DTA UI or after you >> connect >> to the server and the connection dialog goes away? >> - if this is the second case (error after connecting) does the problem >> occur >> if you simply Cancel the connection dialog? >> - have you tried command-line DTA to see if it work? Run 'dta.exe /?' to >> see >> the options if you have not seen it yet. >> - does the error message contain any more information? >> - can you check if at the time you see the error there is a >> dtaengine90.exe >> process running on your system? >> >> Thanks, >> Maciek >> >> >> "Todd C" <To***@discussions.microsoft.com> wrote in message >> news:438AAABC-1BA2-4677-B272-5D7766BEF9E2@microsoft.com... >> >I am running SQL 2005 Standard, obtained from a recent Launch event. >> > >> > I got the Database Engine Tuning Advisor to run only once. Everytime >> > after >> > that I get a runtime error: "R6031 Attempt to initialize the CRT more >> > than >> > once. This indicates a bug in your application." >> > >> > I had the same problem with the Sept. CTP release. Re-booting the >> > machine >> > does not solve this problem. Basicaly, this is a useless tool if I need >> > to >> > un-install and re-install it everytime I need to use it. I have tried >> > deleting all the sessions and creating a new one, re-booting. >> > >> > Any ideas how to solve this? Do I need to wait for a Service Pack? >> >> >> I'm experiencing the same problem. See my answers below.
"Maciek Sarnowicz [MSFT]" <mac***@online.microsoft.com> wrote in message It happens after I connect to the server and the connection dialog goes news:OnFxcW0$FHA.2392@TK2MSFTNGP09.phx.gbl... > We are looking at the issue currently. It has been reported by a few other > people. Please gi ve us some more detail: > > - does this happen immiediately after you start DTA UI or after you > connect to the server and the connection dialog goes away? away. > - if this is the second case (error after connecting) does the problem The problem does not occur if I press the Cancel button at the connection > occur if you simply Cancel the connection dialog? dialog. But the problem does occur if I thereafter attempt to connect from within the DTA. > - have you tried command-line DTA to see if it work? Run 'dta.exe /?' to I tried using the command-line and had the same problem.> see the options if you have not seen it yet. > - does the error message contain any more information? It's a very vague message. Similar to Todd, I get the following:Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\Progr... R6031 Attempt to initialize the CRT more than once. This indicates a bug in your application. > - can you check if at the time you see the error there is a Yes, both dtaengine90.exe and DTASHELL.EXE are loaded. My only recourse is > dtaengine90.exe process running on your system? to kill both processes. Chris Show quote > > Thanks, > Maciek > > > "Todd C" <To***@discussions.microsoft.com> wrote in message > news:438AAABC-1BA2-4677-B272-5D7766BEF9E2@microsoft.com... >>I am running SQL 2005 Standard, obtained from a recent Launch event. >> >> I got the Database Engine Tuning Advisor to run only once. Everytime >> after >> that I get a runtime error: "R6031 Attempt to initialize the CRT more >> than >> once. This indicates a bug in your application." >> >> I had the same problem with the Sept. CTP release. Re-booting the machine >> does not solve this problem. Basicaly, this is a useless tool if I need >> to >> un-install and re-install it everytime I need to use it. I have tried >> deleting all the sessions and creating a new one, re-booting. >> >> Any ideas how to solve this? Do I need to wait for a Service Pack? > > >> - have you tried command-line DTA to see if it work? Run 'dta.exe /?' to BTW, after returning to the command line, I see the following:>> see the options if you have not seen it yet. > > I tried using the command-line and had the same problem. "Failed to initialize MSDB database for tuning (exit code: 1)." Chris Thanks Chris.
This confirms what Todd has reported. We are closing down on the issue, please stay tuned. Regards, Maciek Sarnowicz -------------------- SQL Server SDE This posting is provided "AS IS" with no warranties, and confers no rights Show quote "Chris" <chris@newsgroup.nospam> wrote in message news:erbS$VRAGHA.2132@TK2MSFTNGP14.phx.gbl... >>> - have you tried command-line DTA to see if it work? Run 'dta.exe /?' to >>> see the options if you have not seen it yet. >> >> I tried using the command-line and had the same problem. > > BTW, after returning to the command line, I see the following: > > "Failed to initialize MSDB database for tuning (exit code: 1)." > > Chris > I am having the same exact problem. I de-installed everything and
re-installed to no avail. All other tools and services are working fine so far. I have never been able to "connect to the database using DTA". If I hit cancel at the login, there is no error. When I try to connect the same error is thrown on my machine. What is interesting is I just did a very clean install on my computer less than 30 days ago. The only install issue was that I was not running IIS for reporting services as it is not needed for me. I am running XP Pro with all SP and updates and .Net/updates prior to SQL 2005 Developer Install. Software would be Office 03 and misc business apps. Hope the problem is solved soon. Thank you, kirk Show quote "Maciek Sarnowicz [MSFT]" wrote: > Thanks Chris. > This confirms what Todd has reported. We are closing down on the issue, > please stay tuned. > > > Regards, > Maciek Sarnowicz > -------------------- > SQL Server SDE > > This posting is provided "AS IS" with no warranties, and confers no rights > > > "Chris" <chris@newsgroup.nospam> wrote in message > news:erbS$VRAGHA.2132@TK2MSFTNGP14.phx.gbl... > >>> - have you tried command-line DTA to see if it work? Run 'dta.exe /?' to > >>> see the options if you have not seen it yet. > >> > >> I tried using the command-line and had the same problem. > > > > BTW, after returning to the command line, I see the following: > > > > "Failed to initialize MSDB database for tuning (exit code: 1)." > > > > Chris > > > > > Anything new to report on this? Thanks.
Show quote "Maciek Sarnowicz [MSFT]" <mac***@online.microsoft.com> wrote in message news:OctJ8zTAGHA.3976@TK2MSFTNGP09.phx.gbl... > Thanks Chris. > This confirms what Todd has reported. We are closing down on the issue, > please stay tuned. > > > Regards, > Maciek Sarnowicz > -------------------- > SQL Server SDE > > This posting is provided "AS IS" with no warranties, and confers no rights > > > "Chris" <chris@newsgroup.nospam> wrote in message > news:erbS$VRAGHA.2132@TK2MSFTNGP14.phx.gbl... >>>> - have you tried command-line DTA to see if it work? Run 'dta.exe /?' >>>> to see the options if you have not seen it yet. >>> >>> I tried using the command-line and had the same problem. >> >> BTW, after returning to the command line, I see the following: >> >> "Failed to initialize MSDB database for tuning (exit code: 1)." >> >> Chris >> > > Hi Chris
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\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\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 Chris wrote: Show quote > Anything new to report on this? Thanks. > > "Maciek Sarnowicz [MSFT]" <mac***@online.microsoft.com> wrote in message > news:OctJ8zTAGHA.3976@TK2MSFTNGP09.phx.gbl... > > Thanks Chris. > > This confirms what Todd has reported. We are closing down on the issue, > > please stay tuned. > > > > > > Regards, > > Maciek Sarnowicz > > -------------------- > > SQL Server SDE > > > > This posting is provided "AS IS" with no warranties, and confers no rights > > > > > > "Chris" <chris@newsgroup.nospam> wrote in message > > news:erbS$VRAGHA.2132@TK2MSFTNGP14.phx.gbl... > >>>> - have you tried command-line DTA to see if it work? Run 'dta.exe /?' > >>>> to see the options if you have not seen it yet. > >>> > >>> I tried using the command-line and had the same problem. > >> > >> BTW, after returning to the command line, I see the following: > >> > >> "Failed to initialize MSDB database for tuning (exit code: 1)." > >> > >> Chris > >> > > > > We have identified this to be a problem caused by AppCompat layer in Windows
OS. For overview of AppCompat technology please see here: http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx 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. As already explained by Manoj this can be done by editing system registry. Start the regedit tool and navigate to the following registry key: HKLM\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\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, we 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. Thanks everyone who reported this and helped us with the investigation. Regards, Maciek Sarnowicz -------------------- SQL Server SDE This posting is provided "AS IS" with no warranties, and confers no rights <mano***@hotmail.com> wrote in message Show quote news:1135972316.647065.136070@g14g2000cwa.googlegroups.com... > > Hi Chris > 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\Microsoft\Windows > NT\CurrentVersion\AppCompatFlags\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 > > > > > Chris wrote: >> Anything new to report on this? Thanks. >> >> "Maciek Sarnowicz [MSFT]" <mac***@online.microsoft.com> wrote in message >> news:OctJ8zTAGHA.3976@TK2MSFTNGP09.phx.gbl... >> > Thanks Chris. >> > This confirms what Todd has reported. We are closing down on the issue, >> > please stay tuned. >> > >> > >> > Regards, >> > Maciek Sarnowicz >> > -------------------- >> > SQL Server SDE >> > >> > This posting is provided "AS IS" with no warranties, and confers no >> > rights >> > >> > >> > "Chris" <chris@newsgroup.nospam> wrote in message >> > news:erbS$VRAGHA.2132@TK2MSFTNGP14.phx.gbl... >> >>>> - have you tried command-line DTA to see if it work? Run 'dta.exe >> >>>> /?' >> >>>> to see the options if you have not seen it yet. >> >>> >> >>> I tried using the command-line and had the same problem. >> >> >> >> BTW, after returning to the command line, I see the following: >> >> >> >> "Failed to initialize MSDB database for tuning (exit code: 1)." >> >> >> >> Chris >> >> >> > >> > > I used the suggestion above and DTA now works for me. Thanks for the
temporary fix. Kirk Show quote "Maciek Sarnowicz [MSFT]" wrote: > We have identified this to be a problem caused by AppCompat layer in Windows > OS. > For overview of AppCompat technology please see here: > http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx > 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. As already explained by Manoj this can be done by > editing system registry. Start the regedit tool and navigate to the > following registry key: > HKLM\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\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, we 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. Thanks everyone > who reported this and helped us with the investigation. > > Regards, > Maciek Sarnowicz > -------------------- > SQL Server SDE > > This posting is provided "AS IS" with no warranties, and confers no rights > > > > > <mano***@hotmail.com> wrote in message > news:1135972316.647065.136070@g14g2000cwa.googlegroups.com... > > > > Hi Chris > > 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\Microsoft\Windows > > NT\CurrentVersion\AppCompatFlags\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 > > > > > > > > > > Chris wrote: > >> Anything new to report on this? Thanks. > >> > >> "Maciek Sarnowicz [MSFT]" <mac***@online.microsoft.com> wrote in message > >> news:OctJ8zTAGHA.3976@TK2MSFTNGP09.phx.gbl... > >> > Thanks Chris. > >> > This confirms what Todd has reported. We are closing down on the issue, > >> > please stay tuned. > >> > > >> > > >> > Regards, > >> > Maciek Sarnowicz > >> > -------------------- > >> > SQL Server SDE > >> > > >> > This posting is provided "AS IS" with no warranties, and confers no > >> > rights > >> > > >> > > >> > "Chris" <chris@newsgroup.nospam> wrote in message > >> > news:erbS$VRAGHA.2132@TK2MSFTNGP14.phx.gbl... > >> >>>> - have you tried command-line DTA to see if it work? Run 'dta.exe > >> >>>> /?' > >> >>>> to see the options if you have not seen it yet. > >> >>> > >> >>> I tried using the command-line and had the same problem. > >> >> > >> >> BTW, after returning to the command line, I see the following: > >> >> > >> >> "Failed to initialize MSDB database for tuning (exit code: 1)." > >> >> > >> >> Chris > >> >> > >> > > >> > > > > > >  |
|||||||||||||||||||||||
Other interesting topics