| Groups | Blog | Home |
visual studio .net general : Rebuild Solution causes MS SQL Server 2005 Install cycle to start
I am running VS 2005 with SP1 and SP1 for Vista Beta (running on Vista
Ultimate). In addition I have SQL 2005 Developers Ed with SP2 (not the CTP) running on the same machine. I have a VB application (which does in fact have data adapters and other connectivity objects). When I Rebuild Solution in Release Configuration I get the following 2 dialog boxes which I assume are related to SQL Server 2005 installations. The first dialog box's text is: Microsoft SQL Server 2005 Tools. I the box it says " Please wait while Windows configures Microsoft SQL Server 2005 Tools." The second dialog box's text is: Microsoft SQL Server 2005 Tools. In the box it says "0:Watson 1:1304 2:StreamSupportFiles 3:streamBinaryToDisk 4:5 5:e:\sql9_sp2_t\sql\setup\darwin\sqlcastub\streamca.cpp 6:238 7:stlcastub.dll 8:sqlrun.msi. The compilation stops until I cancel out of these dialog boxes. The compilation then seems to proceed without errors, but, who knows? Any suggestions? --
Hello Michael,
From your description, for one of your VS 2005 project, when you peform building against it, you'll encounter some popup messages indicating the SQL Server is doing some certain configuration, correct? Based on the popup message you provided, it seems the problem is related to the SQL Server management tools, so far I have found some similar issue about the SQL Server integration service(SSIS) or Notification service, when the certain SSIS service account doesn't have sufficient permission or the service can not be accessible from the user account(of the application user), it will try launch the msi setup package to install the certain service. So I'm wondering some further info about your vs 2005 project. Is it a setup project that use SQL Server merge modules or anything else that related to the SQL Server? also, for those existing issue, some of them are caused by insufficient permission to some files or registry path, therefore, for general troubleshooting, you can also use the filemon and regmon tools to montior the file and registry accessing on the machine while building the project. In addition, you can try building the same project on some other box to confirm whether this is specific to the machine environment. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Thanks for your reply. This Solution has a Setup project in it but has no SQL
Server Merge modules. The only thing that the Solution has to do with SQL Server is that it uses ADO .NET to access data on a SQL Server 2005. The problem seems to occur only with this Solution but I have not yet identified if it occurs with this Solution on another similarly configured development machine. I have never used filemon or regmon but will be willling to try if it help identify the cause. Any links to short instruction sets? The instance on SQL Server is on the development machine and all services use the same administrator permissions. I guess I could look further into the specific permissions granted for each service and to make sure the services are started. I'm now on a different development machine and the Build All in Release config seemed to work without generating the errors noted previously. Now however, I'm getting a Delayed Write Failure e:\$mft messages. This is new, very odd, especially because my e drive is a DVD burner. BTW, this new development machine is XP, not Vista. There must be something in this compilation that is reacting to the SP2 of SQL Server 2005 because it never happened prior to it's installation and it's common to both development machines. -- Michael Hockstein [quoted text, click to view] "Steven Cheng[MSFT]" wrote:
> Hello Michael, > > From your description, for one of your VS 2005 project, when you peform > building against it, you'll encounter some popup messages indicating the > SQL Server is doing some certain configuration, correct? > > Based on the popup message you provided, it seems the problem is related to > the SQL Server management tools, so far I have found some similar issue > about the SQL Server integration service(SSIS) or Notification service, > when the certain SSIS service account doesn't have sufficient permission or > the service can not be accessible from the user account(of the application > user), it will try launch the msi setup package to install the certain > service. So I'm wondering some further info about your vs 2005 project. Is > it a setup project that use SQL Server merge modules or anything else that > related to the SQL Server? > > also, for those existing issue, some of them are caused by insufficient > permission to some files or registry path, therefore, for general > troubleshooting, you can also use the filemon and regmon tools to montior > the file and registry accessing on the machine while building the project. > > In addition, you can try building the same project on some other box to > confirm whether this is specific to the machine environment. > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > > > ================================================== > > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > > ================================================== > > > > This posting is provided "AS IS" with no warranties, and confers no rights. >
Thanks for your reply Michael,
For regmon and filemon, you can find sufficient information on using them in the following site: #FileMon for Windows v7.04 http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx #RegMon for Windows v7.04 http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx Also, as for the "Sql server 2005 SP2", I think this does be an clues since it may have changed some certain settings of the SQL Server servcie. Anyway, you can even try uninstalling the SP2 to verify this. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
I installed ProcMon instead. I was able to see where .msi started but
couldn't figure out what was calling it or why. There is a lot of data produced by ProcMon! I tried changing the Log On's of all the SQL Server services without much success. I have concluded that the phenomenon only occurs when building in Release configuration and there is a Setup project in the solution. I think, but am not yet sure, that if I start VS 2005 with "Run as Administrator" instead of just double-clicking on the .sln of my application, the phenomenon goes away. -- Michael Hockstein [quoted text, click to view] "Steven Cheng[MSFT]" wrote:
> Thanks for your reply Michael, > > For regmon and filemon, you can find sufficient information on using them > in the following site: > > #FileMon for Windows v7.04 > http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx > > #RegMon for Windows v7.04 > http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx > > Also, as for the "Sql server 2005 SP2", I think this does be an clues since > it may have changed some certain settings of the SQL Server servcie. > Anyway, you can even try uninstalling the SP2 to verify this. > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > > This posting is provided "AS IS" with no warranties, and confers no rights. >
Thanks for your reply Michael,
For the "start VS 2005 with "Run as Administrator"", this does be the recommended approach on windows Vista, however, have you tested this with some other setup or ADO.NET data access project to see whether this is the cause? Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
I didn't have any other Solutions to test on the machine. It's a new Vista
installation and I have few projects on it. However, starting from Run as Admin seems to work. Now if the VS 2005 VB IDE surface could be improved to facilitate Vista app dev. Is there a VS 2007? -- Michael Hockstein [quoted text, click to view] "Steven Cheng[MSFT]" wrote:
> Thanks for your reply Michael, > > For the "start VS 2005 with "Run as Administrator"", this does be the > recommended approach on windows Vista, however, have you tested this with > some other setup or ADO.NET data access project to see whether this is the > cause? > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > > This posting is provided "AS IS" with no warranties, and confers no rights. >
Thanks for your reply Michael,
As for the "facilitate Vista app dev" you mentioned, do you mean developing .NET framework 3.0 applications(WPF, WCF, WWF...)? If so, this is supported with VS 2005 and you need to install an extension: #Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November 2006 CTP http://www.microsoft.com/downloads/details.aspx?familyid=F54F5537-CC86-4BF5- AE44-F5A1E805680D&displaylang=en Also, you can have a look at the following articles to get all the components you need to install for developing .net 3.0 application(some of them is preinstalled on windows vista): http://www.netfx3.com/blogs/news_and_announcements/archive/2006/11/06/.NET-F ramework-3.0-has-been-released_2100_.aspx here are some other good articles on .net 3.0 versioning and setup a development environment: http://blogs.msdn.com/tims/archive/2006/12/20/building-a-perfect-wpf-develop er-workstation.aspx http://msdn2.microsoft.com/en-us/winfx/aa663314.aspx In addition, the Visual Studio 2007(code name Orcas) is still under developing. Currently, there is CTP version available. You can find the latest download here: #Visual Studio Code Name "Orcas" Related CTP Downloads http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx Hope this helps. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
Actually, for now, I want my .NET 2.0 Solutions to build in compliance and
run with the appropriate tokens on Vista. But, I think that we're already discussing this in another thread. -- Michael Hockstein [quoted text, click to view] "Steven Cheng[MSFT]" wrote:
> Thanks for your reply Michael, > > As for the "facilitate Vista app dev" you mentioned, do you mean developing > .NET framework 3.0 applications(WPF, WCF, WWF...)? If so, this is supported > with VS 2005 and you need to install an extension: > > #Visual Studio 2005 extensions for .NET Framework 3.0 (WCF & WPF), November > 2006 CTP > http://www.microsoft.com/downloads/details.aspx?familyid=F54F5537-CC86-4BF5- > AE44-F5A1E805680D&displaylang=en > > Also, you can have a look at the following articles to get all the > components you need to install for developing .net 3.0 application(some of > them is preinstalled on windows vista): > > http://www.netfx3.com/blogs/news_and_announcements/archive/2006/11/06/.NET-F > ramework-3.0-has-been-released_2100_.aspx > > here are some other good articles on .net 3.0 versioning and setup a > development environment: > > http://blogs.msdn.com/tims/archive/2006/12/20/building-a-perfect-wpf-develop > er-workstation.aspx > > http://msdn2.microsoft.com/en-us/winfx/aa663314.aspx > > In addition, the Visual Studio 2007(code name Orcas) is still under > developing. Currently, there is CTP version available. You can find the > latest download here: > > #Visual Studio Code Name "Orcas" Related CTP Downloads > http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx > > Hope this helps. > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > > This posting is provided "AS IS" with no warranties, and confers no rights. >
Thanks for your reply Michael,
For building .net framework 2.0 appliation, there is no different from doing it on xp or 2003 box. And for token, do you mean the security token? If so, it is a standard behavior on windows Vista operating system, not specifci to .net framework or other application. As long as you enable the UAC(by default), it will always prompt for approval on privileged operations if you haven't run the program as admin privilege. As you have got, following this rule, vista compatible application should use a manifest file to demand the required security privilege so that the UAC will prompt for the sufficient token at begining of the program. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |