Also posted in the MSDE section...
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>
Showing posts with label install. Show all posts
Showing posts with label install. Show all posts
Friday, March 23, 2012
ODBC connection problems....
Also posted in the MSDE section...
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.
Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.
Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>
ODBC connection problems....
Also posted in the MSDE section...
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>sql
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>sql
ODBC Connection Problem
Hello,
I have an install of SQL that my users cannot connect to with an ODBC
connection. I have created Windows User logins on the SQL server through
Enterprise Manager, and have assigned them access to one specific database.
The specific user accounts have public, db_datareader and db_datawriter
permissions to the database. When the users attemtpt to create their ODBC
connections they receive an access denied message. What other permissions do
I need to give these users? Do they need any other permissions to the actual
server the SQL instance resides on?
Thanks,
JBaileyJBailey,
Please let me know the following:
- These accounts that you created to access that datbase, can they connect
and query the database from query analyser?
- Also, could you please created a UDL to test for connectivity (this gives
us a good idea if the odbc connection is ok). Also it could be that we
arent passing the correct 'connection string'?
Create a text file and name it <anything>.UDL. Rt-click the UDL file and
select Properties. The Connection tab contains all the fields exposed to
the application, and you choose the appropriate items to be filled in to
successfully "Test Connection" before you are able to use it. Once the Test
button works, click on OK and open up the UDL file in Notepad. Its just a
text file, and contains a provider string that you should be able to paste
into your application or whichever application is calling the sql server.
Cheers!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
I have an install of SQL that my users cannot connect to with an ODBC
connection. I have created Windows User logins on the SQL server through
Enterprise Manager, and have assigned them access to one specific database.
The specific user accounts have public, db_datareader and db_datawriter
permissions to the database. When the users attemtpt to create their ODBC
connections they receive an access denied message. What other permissions do
I need to give these users? Do they need any other permissions to the actual
server the SQL instance resides on?
Thanks,
JBaileyJBailey,
Please let me know the following:
- These accounts that you created to access that datbase, can they connect
and query the database from query analyser?
- Also, could you please created a UDL to test for connectivity (this gives
us a good idea if the odbc connection is ok). Also it could be that we
arent passing the correct 'connection string'?
Create a text file and name it <anything>.UDL. Rt-click the UDL file and
select Properties. The Connection tab contains all the fields exposed to
the application, and you choose the appropriate items to be filled in to
successfully "Test Connection" before you are able to use it. Once the Test
button works, click on OK and open up the UDL file in Notepad. Its just a
text file, and contains a provider string that you should be able to paste
into your application or whichever application is calling the sql server.
Cheers!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
Monday, March 19, 2012
ODBC and SQLServer : does I need the client installed on ?
Hi,
Does I need to install the mssql client binaries to use ODBC to
connect to a mssql database ?
TYIA
rjp"rjp" <rjp.l@.laposte.net> wrote in message
news:9b7a7215.0402100934.5fe5b830@.posting.google.c om...
> Hi,
> Does I need to install the mssql client binaries to use ODBC to
> connect to a mssql database ?
> TYIA
> rjp
You should be able to use the latest version of MDAC - there's a link from
this page:
http://msdn.microsoft.com/data/
Simon|||rjp (rjp.l@.laposte.net) writes:
> Does I need to install the mssql client binaries to use ODBC to
> connect to a mssql database ?
ODBC comes with MDAC that comes with Windows, so you don't need to install
anything - if you are on a Windows box, that is. (And it's a decently
modern version of Windows. Windows 95 is not likely to have any MDAC.)
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Friday, March 9, 2012
ODBC
I go to install sql server 2000 in one of our servers, would like to
know if after the installation I lose connections ODBC that already I
possess using SQL Server 7If the database names and the servernames are the same ( like in an
upgrade ) the ODBC DSNs need not be changed. Otherwise you'll have to click
configure and reset the values.
--
- Anith
( Please reply to newsgroups only )
know if after the installation I lose connections ODBC that already I
possess using SQL Server 7If the database names and the servernames are the same ( like in an
upgrade ) the ODBC DSNs need not be changed. Otherwise you'll have to click
configure and reset the values.
--
- Anith
( Please reply to newsgroups only )
ODBC
Hi,
Using VB.NET how can I deploy ODBC connection to automatically install when
the package is installed?
YamaConsider using a DSN-less connection. Then there is nothing to distribute.
313295 HOW TO: Use the Server Name Parameter in a Connection String to
Specify
http://support.microsoft.com/?id=313295
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin,
But I had to create the ODBC package for my company legacy program written
in FoxPro!!!
Using InstallShield I was able to distribute the ODBC.
I wrote to the registry the following:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\myDSNName]
"Driver"= %windir% + "\\system32\\SQLSRV32.dll"
"Server"="myServer"
"Database"="myDatabase"
"LastUser"="sa"
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"myDSNName"="SQL Server"
Thank you,
Yama
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:RWwjZsL1DHA.3564@.cpmsftngxa07.phx.gbl...
distribute.
Using VB.NET how can I deploy ODBC connection to automatically install when
the package is installed?
YamaConsider using a DSN-less connection. Then there is nothing to distribute.
313295 HOW TO: Use the Server Name Parameter in a Connection String to
Specify
http://support.microsoft.com/?id=313295
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin,
But I had to create the ODBC package for my company legacy program written
in FoxPro!!!
Using InstallShield I was able to distribute the ODBC.
I wrote to the registry the following:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\myDSNName]
"Driver"= %windir% + "\\system32\\SQLSRV32.dll"
"Server"="myServer"
"Database"="myDatabase"
"LastUser"="sa"
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"myDSNName"="SQL Server"
Thank you,
Yama
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:RWwjZsL1DHA.3564@.cpmsftngxa07.phx.gbl...
quote:
> Consider using a DSN-less connection. Then there is nothing to
distribute.
quote:
> 313295 HOW TO: Use the Server Name Parameter in a Connection String to
> Specify
> http://support.microsoft.com/?id=313295
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
ODBC
Does the install for the Desktop Engine include the ODBC drivers?
Yes, All SQL Servers will install MDAC (of which ODBC is part of) 2.6, unless you already have an MDAC with
higher version on your system.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Jeff" <anonymous@.discussions.microsoft.com> wrote in message
news:635BDE4A-11C1-456A-A7B3-B318B624AF93@.microsoft.com...
> Does the install for the Desktop Engine include the ODBC drivers?
Yes, All SQL Servers will install MDAC (of which ODBC is part of) 2.6, unless you already have an MDAC with
higher version on your system.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Jeff" <anonymous@.discussions.microsoft.com> wrote in message
news:635BDE4A-11C1-456A-A7B3-B318B624AF93@.microsoft.com...
> Does the install for the Desktop Engine include the ODBC drivers?
Wednesday, March 7, 2012
Obtaining SQL RSS Developer Addition
I want to install SQL Reporting Services on my laptop which has Windows XP
Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
Where can I download or obtain the install file for SQL Reporting Services
Developer Edition?
- MaxI tried the same question a while ago with no reply out here.
No I bought msdn pro subscription to get visual studio and here I can
download rep s dev. edition as well.
You should think that you could get it for free if you have sql 2000 dev
edition, though...
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||What are you trying to achieve Max?, the Reporting Services server-part does
not run on MSDE you can't install the reports-database on MSDE and it also
needs IIS to host the reports website.
Ed
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
>I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||But you have different versions of rep s as welle as different versions of
sql server:
developers ediition
standard edition
entreprise edition
dev ed is much cheaper and can be used for dev purposes.
"Ed Richard" <Ed_XXX_@.wss-ed_REMOVE_.nl> wrote in message
news:%23mIKQ8tgFHA.3788@.tk2msftngp13.phx.gbl...
> What are you trying to achieve Max?, the Reporting Services server-part
does
> not run on MSDE you can't install the reports-database on MSDE and it also
> needs IIS to host the reports website.
> Ed
> "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> >I want to install SQL Reporting Services on my laptop which has Windows
XP
> > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> >
> > Where can I download or obtain the install file for SQL Reporting
Services
> > Developer Edition?
> >
> > - Max
>|||I got lucky and found someone who had the setup file for SQL RSS Dev.
Edition. I am using it on SQL Dev Edition, not SQL MSDE (Desktop Edition).
And running iis on WinXP as well. All are working fine on my XP machine now.
"Michael Vardinghus" wrote:
> But you have different versions of rep s as welle as different versions of
> sql server:
> developers ediition
> standard edition
> entreprise edition
> dev ed is much cheaper and can be used for dev purposes.
> "Ed Richard" <Ed_XXX_@.wss-ed_REMOVE_.nl> wrote in message
> news:%23mIKQ8tgFHA.3788@.tk2msftngp13.phx.gbl...
> > What are you trying to achieve Max?, the Reporting Services server-part
> does
> > not run on MSDE you can't install the reports-database on MSDE and it also
> > needs IIS to host the reports website.
> >
> > Ed
> >
> > "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> > news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> > >I want to install SQL Reporting Services on my laptop which has Windows
> XP
> > > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> > >
> > > Where can I download or obtain the install file for SQL Reporting
> Services
> > > Developer Edition?
> > >
> > > - Max
> >
> >
>
>|||You can order a CD here:
http://www.microsoft.com/sql/reporting/howtobuy/retailfulfillment.mspx
Ed
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
>I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||Hi,
This discussion is probably closed, but maybe you can still help me.
Could anyone ever find a link to download the Reporting Services Developer
Edition?
I have Reporting Services Evaluation Edition on my XP machine, but I wonder
what will happen when the 120 day trial duration expires and therefore wanna
install the developer edition.
Thanks,
Gul
"Ed Richard" wrote:
> You can order a CD here:
> http://www.microsoft.com/sql/reporting/howtobuy/retailfulfillment.mspx
> Ed
> "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> >I want to install SQL Reporting Services on my laptop which has Windows XP
> > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> >
> > Where can I download or obtain the install file for SQL Reporting Services
> > Developer Edition?
> >
> > - Max
>
>
Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
Where can I download or obtain the install file for SQL Reporting Services
Developer Edition?
- MaxI tried the same question a while ago with no reply out here.
No I bought msdn pro subscription to get visual studio and here I can
download rep s dev. edition as well.
You should think that you could get it for free if you have sql 2000 dev
edition, though...
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||What are you trying to achieve Max?, the Reporting Services server-part does
not run on MSDE you can't install the reports-database on MSDE and it also
needs IIS to host the reports website.
Ed
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
>I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||But you have different versions of rep s as welle as different versions of
sql server:
developers ediition
standard edition
entreprise edition
dev ed is much cheaper and can be used for dev purposes.
"Ed Richard" <Ed_XXX_@.wss-ed_REMOVE_.nl> wrote in message
news:%23mIKQ8tgFHA.3788@.tk2msftngp13.phx.gbl...
> What are you trying to achieve Max?, the Reporting Services server-part
does
> not run on MSDE you can't install the reports-database on MSDE and it also
> needs IIS to host the reports website.
> Ed
> "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> >I want to install SQL Reporting Services on my laptop which has Windows
XP
> > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> >
> > Where can I download or obtain the install file for SQL Reporting
Services
> > Developer Edition?
> >
> > - Max
>|||I got lucky and found someone who had the setup file for SQL RSS Dev.
Edition. I am using it on SQL Dev Edition, not SQL MSDE (Desktop Edition).
And running iis on WinXP as well. All are working fine on my XP machine now.
"Michael Vardinghus" wrote:
> But you have different versions of rep s as welle as different versions of
> sql server:
> developers ediition
> standard edition
> entreprise edition
> dev ed is much cheaper and can be used for dev purposes.
> "Ed Richard" <Ed_XXX_@.wss-ed_REMOVE_.nl> wrote in message
> news:%23mIKQ8tgFHA.3788@.tk2msftngp13.phx.gbl...
> > What are you trying to achieve Max?, the Reporting Services server-part
> does
> > not run on MSDE you can't install the reports-database on MSDE and it also
> > needs IIS to host the reports website.
> >
> > Ed
> >
> > "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> > news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> > >I want to install SQL Reporting Services on my laptop which has Windows
> XP
> > > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> > >
> > > Where can I download or obtain the install file for SQL Reporting
> Services
> > > Developer Edition?
> > >
> > > - Max
> >
> >
>
>|||You can order a CD here:
http://www.microsoft.com/sql/reporting/howtobuy/retailfulfillment.mspx
Ed
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
>I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||Hi,
This discussion is probably closed, but maybe you can still help me.
Could anyone ever find a link to download the Reporting Services Developer
Edition?
I have Reporting Services Evaluation Edition on my XP machine, but I wonder
what will happen when the 120 day trial duration expires and therefore wanna
install the developer edition.
Thanks,
Gul
"Ed Richard" wrote:
> You can order a CD here:
> http://www.microsoft.com/sql/reporting/howtobuy/retailfulfillment.mspx
> Ed
> "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> >I want to install SQL Reporting Services on my laptop which has Windows XP
> > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> >
> > Where can I download or obtain the install file for SQL Reporting Services
> > Developer Edition?
> >
> > - Max
>
>
Obtaining PATH to master DB
I need to obtain the path to the master DB in a Wise install script. I know that for SQL2K it is in the registry key:
HKLM\Software\Microsoft\MSSQLServer\Setup
It seems that a SQL2005 installation does not have the same default
directory.
Is there a way to query this from the server itself so I don't have to read the registry?With the usual caveat that it is not a 'best practice' to query the system tables, you can find the answer by executing:
SELECT filename
FROM sysfiles
while connected to the master database. You will get two records. One is the data file, one is the log file. You can narrow the query by adding:
WHERE name = 'master'
Regards,
hmscott
Edit to add: I did verify this against a SQL 2005 instance we are running in development, but it will also work in SQL2K.
HKLM\Software\Microsoft\MSSQLServer\Setup
It seems that a SQL2005 installation does not have the same default
directory.
Is there a way to query this from the server itself so I don't have to read the registry?With the usual caveat that it is not a 'best practice' to query the system tables, you can find the answer by executing:
SELECT filename
FROM sysfiles
while connected to the master database. You will get two records. One is the data file, one is the log file. You can narrow the query by adding:
WHERE name = 'master'
Regards,
hmscott
Edit to add: I did verify this against a SQL 2005 instance we are running in development, but it will also work in SQL2K.
Monday, February 20, 2012
Obscure error while attempting to install SQL Server 2005 SP1
I successfully installed SQL Server 2005 SP1 on one PC. When I attempt to install it on a second PC, however, I get the following obscure error:
Unexpected Error Occurred
The following unexpected error occurred:
That's right, there's nothing else listed, other an OK button. D'oh! When I press the OK button, the following error report dialog box appears:
Hotfix.exe
A recently applied update, NULL, failed to install.
There are no pending updates that I'm aware of, as I just booted the PC. I sent the error report.
I notice on this particular PC that the SP1 install EXE is expanding/writing to an external SCSI drive; would that make a difference? I don't see a way to specify a different (i.e., internal ATA drive).
Any other ideas?
You need to look in the setup log files to track down the problem. They're located here:
%\Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
There's also a summary.txt file up one directory and it may point you to the right log file. If you have trouble interpreting the results, please post the errors here and we'll see if we can help you out.
Paul
|||Thanks. Before I delve further into the log file, I noticed that Summary.txt indicates everything is fine, although I don't understand the references to "Uninstall":
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Apr 14 00:07:10 2006
Machine : PC001
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Uninstall : Successful , Reboot required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQL.log
--
Machine : PC001
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQLSupport_1.log
--
Machine : PC001
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SqlWriter_1.log
--
Machine : PC001
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_MSXML6_1.log
--
Setup succeeded with the installation, inspect the log file completely for status on all the components.Time : Fri Apr 14 01:30:27 2006
I'm not sure why the first section says "Microsoft SQL Server 2005 Express Edition". I don't have the Express Edition installed on this PC, although I installed and uninstalled it a few months ago. Indeed, the Express Edition doesn't appear within the "Add or Remove Programs" applet.
I welcome your suggestions as to how to proceed.
|||If it's any comfort, you are not the only one with this error.
Installed fine the first time on my development server where it is a clean install of Windows 2003 and SQL 2005. However on the pc’s I have attempted to install on, where there is Visual Studio and Office installed it refuses to install.
I have tried on 3 other PC's and they all suffer the same way.
|||
Problem solved.
I took the time over the weekend ( I need to get a life) to build a clean OS install and install SQL 2005 developer edition and then install the service pack to see when and where it broke.
The issue seems to be associated with the fact that the SQL 2005 developer edition I was trying to upgrade was from the ISO image downloaded from the MSDN website. I uninstalled the ISO image and installed SQL from the MSDN subscription CD's and the service pack installs fine.
Can someone at Microsoft please confirm this is an issue!
|||
Interesting observation, Des; thanks. My install came from the ISO image downloaded from the MSDN website, also.
How do you know that simply uninstalling and re-installing didn't resolve the problem?
|||I actually reinstalled from the ISO image first with the same result.
I then went hunting through boxes of MSDN disks till I found the real disks, and reinstalled from the MSDN media. Once installed from the MSDN media the service pack installed first go.
|||We have ugraded one server with SP1 for SQL 2005 without any issues,but when we performed the same task on other server with the same sp1 setup,we encountered the problem which you experienced "The following unexpected error occurred" Both the servers are installed from the same ISO image of MSDN, Herby I attach the log of the hotfix which I executed.
05/26/2006 10:24:48.546 ================================================================================
05/26/2006 10:24:48.546 Hotfix package launched
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Local Computer:
05/26/2006 10:24:48.609 Target Details: SRC-R-AS10
05/26/2006 10:24:48.609 commonfilesdir = C:\Program Files\Common Files
05/26/2006 10:24:48.609 lcidsupportdir = s:\0596decce11fd6b46f501bbd4cfb\1033
05/26/2006 10:24:48.609 programfilesdir = C:\Program Files
05/26/2006 10:24:48.609 supportdir = \\SRC-R-AS10\s$\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 supportdirlocal = s:\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 windir = C:\WINDOWS
05/26/2006 10:24:48.609 winsysdir = C:\WINDOWS\system32
05/26/2006 10:24:48.609
05/26/2006 10:24:48.656 Enumerating applicable products for this patch
05/26/2006 10:24:53.046 The patch installation could not proceed due to unexpected errors
05/26/2006 10:24:53.046
05/26/2006 10:24:53.046 Product Status Summary:
05/26/2006 10:24:53.171 Hotfix package closed
We experience the same error while installing the hotfix AS2005-KB914595-x86-ENU.exe (this hotfix was installed on other server which upgraded successfully.)
Reinstalling is not a feasible option for our environment.Kindly suggest.
~Vishal
|||I received the same "A recently applied update, NULL, failed to install." error when attempting to install SP1 on SQL Server 2005 Enterprise version. As previously noted, I also uninstalled the ISO version from MSDN and re-installed from the MSDN DVD.
Following the reinstall, I attempted to run the individual hotfixes, starting with sql2005-kb918222-x86-enu.exe. Once again, I received the error.
Finally, I attempted to run the fixed patch noted in KB914595 and received a slightly different message but with the same, unsatisfactory results. The message has now changed to "Uninstallation of the 'NULL' update failed". Note that the installer chose to place the support directory on a SAN connection (F:). Could this be a lead toward a solution?
Here's the log file from the %WINDIR%\Hotfix folder:
08/05/2006 16:22:34.875 ================================================================================
08/05/2006 16:22:34.875 Hotfix package launched
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Local Computer:
08/05/2006 16:22:35.031 Target Details: EMERALD
08/05/2006 16:22:35.031 commonfilesdir = C:\Program Files\Common Files
08/05/2006 16:22:35.031 lcidsupportdir = f:\074fcbd1c0e3fd87748b2a9b748b9208\1033
08/05/2006 16:22:35.031 programfilesdir = C:\Program Files
08/05/2006 16:22:35.031 supportdir = \\EMERALD\f$\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 supportdirlocal = f:\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 windir = C:\WINDOWS
08/05/2006 16:22:35.031 winsysdir = C:\WINDOWS\system32
08/05/2006 16:22:35.031
08/05/2006 16:22:35.093 Enumerating applicable products for this patch
08/05/2006 16:22:36.625 The patch installation could not proceed due to unexpected errors
08/05/2006 16:22:36.625
08/05/2006 16:22:36.625 Product Status Summary:
08/05/2006 16:22:36.843 Hotfix package closed
I think I have a solution to the problem 
After installing/uninstalling SQL Server several times and trying to install SP1, about a dozen or more times, I noticed that in the Hotfix log details (see my earlier posting) that the "lcidsupportdir", "supportdirlocal" and "supportdir" all referred to drive "F:". In the Hotfix log details posted by Vishal_LogicalCMG, these same values refer to drive "S:". On the system where SP-1 was failing, drive "F:" is connected to a SAN (I wonder if there's significance to the drive letter "S:" in Vishal's post?).
Since Hotfix.exe doesn't provide a parameter to specify these values, I guessed that Hotfix.exe simply looks for the drive with the most free space for its workspace. On my system, the SAN had a lot more space than the boot drive. I quickly whipped up a script that created a 1GB file and repeatedly made copies of it on drive F: until drive C: had more free space. (I know it's a hack, but I was desparate by now!)
You guessed it - Hotfix.exe now placed its workfiles on the root drive C: and SQL Server 2005 Enterprise version is running with SP-1 installed! It looks like Hotfix.exe doesn't like to work across a SAN.
Microsoft ... are you listening?
Dave
|||Thank you for help. I had the same problem with installing SP1 for SQL Server 2005. It was caused by running installation from USB harddrive. When I coppied SP1 installation to C: then SP1 and post-SP1 hotfixes installed successfully.|||Dave,
Thanks for your post. I had the same issue, but I was not using a SANS, i just had a second drive that had more free space than the C drive. When i filled up that drive the install worked just fine.
Gotta love the QA over at Microsoft sometimes...... DUH.
Thanks again.
|||An easy workaround is to set up a 1 kb Disk Quota on the Larger Drive, which will force the MSI installer to use the C: drive. :)|||Thanks a million Dave! Genious Stuff
I would have never thought of this solution...but finally I too managed to fix this weird issue with the help of your post.
Cheers!
|||The disk quote workaround did not work for me....
However, here is a slightly less kludgy solution is to go to the properties for each SAN drive (M:, N:, O:, etc) -> Security -> Add
your current username to the list, and Deny -> Full Control. Do this for
each SAN drive and the installer will be forced to use the C: drive. Yay
Caleb
Obscure error while attempting to install SQL Server 2005 SP1
I successfully installed SQL Server 2005 SP1 on one PC. When I attempt to install it on a second PC, however, I get the following obscure error:
Unexpected Error Occurred
The following unexpected error occurred:
That's right, there's nothing else listed, other an OK button. D'oh! When I press the OK button, the following error report dialog box appears:
Hotfix.exe
A recently applied update, NULL, failed to install.
There are no pending updates that I'm aware of, as I just booted the PC. I sent the error report.
I notice on this particular PC that the SP1 install EXE is expanding/writing to an external SCSI drive; would that make a difference? I don't see a way to specify a different (i.e., internal ATA drive).
Any other ideas?
You need to look in the setup log files to track down the problem. They're located here:
%\Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
There's also a summary.txt file up one directory and it may point you to the right log file. If you have trouble interpreting the results, please post the errors here and we'll see if we can help you out.
Paul
|||Thanks. Before I delve further into the log file, I noticed that Summary.txt indicates everything is fine, although I don't understand the references to "Uninstall":
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Apr 14 00:07:10 2006
Machine : PC001
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Uninstall : Successful , Reboot required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQL.log
--
Machine : PC001
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQLSupport_1.log
--
Machine : PC001
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SqlWriter_1.log
--
Machine : PC001
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_MSXML6_1.log
--
Setup succeeded with the installation, inspect the log file completely for status on all the components.Time : Fri Apr 14 01:30:27 2006
I'm not sure why the first section says "Microsoft SQL Server 2005 Express Edition". I don't have the Express Edition installed on this PC, although I installed and uninstalled it a few months ago. Indeed, the Express Edition doesn't appear within the "Add or Remove Programs" applet.
I welcome your suggestions as to how to proceed.
|||If it's any comfort, you are not the only one with this error.
Installed fine the first time on my development server where it is a clean install of Windows 2003 and SQL 2005. However on the pc’s I have attempted to install on, where there is Visual Studio and Office installed it refuses to install.
I have tried on 3 other PC's and they all suffer the same way.
|||
Problem solved.
I took the time over the weekend ( I need to get a life) to build a clean OS install and install SQL 2005 developer edition and then install the service pack to see when and where it broke.
The issue seems to be associated with the fact that the SQL 2005 developer edition I was trying to upgrade was from the ISO image downloaded from the MSDN website. I uninstalled the ISO image and installed SQL from the MSDN subscription CD's and the service pack installs fine.
Can someone at Microsoft please confirm this is an issue!
|||
Interesting observation, Des; thanks. My install came from the ISO image downloaded from the MSDN website, also.
How do you know that simply uninstalling and re-installing didn't resolve the problem?
|||I actually reinstalled from the ISO image first with the same result.
I then went hunting through boxes of MSDN disks till I found the real disks, and reinstalled from the MSDN media. Once installed from the MSDN media the service pack installed first go.
|||We have ugraded one server with SP1 for SQL 2005 without any issues,but when we performed the same task on other server with the same sp1 setup,we encountered the problem which you experienced "The following unexpected error occurred" Both the servers are installed from the same ISO image of MSDN, Herby I attach the log of the hotfix which I executed.
05/26/2006 10:24:48.546 ================================================================================
05/26/2006 10:24:48.546 Hotfix package launched
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Local Computer:
05/26/2006 10:24:48.609 Target Details: SRC-R-AS10
05/26/2006 10:24:48.609 commonfilesdir = C:\Program Files\Common Files
05/26/2006 10:24:48.609 lcidsupportdir = s:\0596decce11fd6b46f501bbd4cfb\1033
05/26/2006 10:24:48.609 programfilesdir = C:\Program Files
05/26/2006 10:24:48.609 supportdir = \\SRC-R-AS10\s$\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 supportdirlocal = s:\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 windir = C:\WINDOWS
05/26/2006 10:24:48.609 winsysdir = C:\WINDOWS\system32
05/26/2006 10:24:48.609
05/26/2006 10:24:48.656 Enumerating applicable products for this patch
05/26/2006 10:24:53.046 The patch installation could not proceed due to unexpected errors
05/26/2006 10:24:53.046
05/26/2006 10:24:53.046 Product Status Summary:
05/26/2006 10:24:53.171 Hotfix package closed
We experience the same error while installing the hotfix AS2005-KB914595-x86-ENU.exe (this hotfix was installed on other server which upgraded successfully.)
Reinstalling is not a feasible option for our environment.Kindly suggest.
~Vishal
|||I received the same "A recently applied update, NULL, failed to install." error when attempting to install SP1 on SQL Server 2005 Enterprise version. As previously noted, I also uninstalled the ISO version from MSDN and re-installed from the MSDN DVD.
Following the reinstall, I attempted to run the individual hotfixes, starting with sql2005-kb918222-x86-enu.exe. Once again, I received the error.
Finally, I attempted to run the fixed patch noted in KB914595 and received a slightly different message but with the same, unsatisfactory results. The message has now changed to "Uninstallation of the 'NULL' update failed". Note that the installer chose to place the support directory on a SAN connection (F:). Could this be a lead toward a solution?
Here's the log file from the %WINDIR%\Hotfix folder:
08/05/2006 16:22:34.875 ================================================================================
08/05/2006 16:22:34.875 Hotfix package launched
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Local Computer:
08/05/2006 16:22:35.031 Target Details: EMERALD
08/05/2006 16:22:35.031 commonfilesdir = C:\Program Files\Common Files
08/05/2006 16:22:35.031 lcidsupportdir = f:\074fcbd1c0e3fd87748b2a9b748b9208\1033
08/05/2006 16:22:35.031 programfilesdir = C:\Program Files
08/05/2006 16:22:35.031 supportdir = \\EMERALD\f$\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 supportdirlocal = f:\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 windir = C:\WINDOWS
08/05/2006 16:22:35.031 winsysdir = C:\WINDOWS\system32
08/05/2006 16:22:35.031
08/05/2006 16:22:35.093 Enumerating applicable products for this patch
08/05/2006 16:22:36.625 The patch installation could not proceed due to unexpected errors
08/05/2006 16:22:36.625
08/05/2006 16:22:36.625 Product Status Summary:
08/05/2006 16:22:36.843 Hotfix package closed
I think I have a solution to the problem 
After installing/uninstalling SQL Server several times and trying to install SP1, about a dozen or more times, I noticed that in the Hotfix log details (see my earlier posting) that the "lcidsupportdir", "supportdirlocal" and "supportdir" all referred to drive "F:". In the Hotfix log details posted by Vishal_LogicalCMG, these same values refer to drive "S:". On the system where SP-1 was failing, drive "F:" is connected to a SAN (I wonder if there's significance to the drive letter "S:" in Vishal's post?).
Since Hotfix.exe doesn't provide a parameter to specify these values, I guessed that Hotfix.exe simply looks for the drive with the most free space for its workspace. On my system, the SAN had a lot more space than the boot drive. I quickly whipped up a script that created a 1GB file and repeatedly made copies of it on drive F: until drive C: had more free space. (I know it's a hack, but I was desparate by now!)
You guessed it - Hotfix.exe now placed its workfiles on the root drive C: and SQL Server 2005 Enterprise version is running with SP-1 installed! It looks like Hotfix.exe doesn't like to work across a SAN.
Microsoft ... are you listening?
Dave
|||Thank you for help. I had the same problem with installing SP1 for SQL Server 2005. It was caused by running installation from USB harddrive. When I coppied SP1 installation to C: then SP1 and post-SP1 hotfixes installed successfully.|||Dave,
Thanks for your post. I had the same issue, but I was not using a SANS, i just had a second drive that had more free space than the C drive. When i filled up that drive the install worked just fine.
Gotta love the QA over at Microsoft sometimes...... DUH.
Thanks again.
|||An easy workaround is to set up a 1 kb Disk Quota on the Larger Drive, which will force the MSI installer to use the C: drive. :)|||Thanks a million Dave! Genious Stuff
I would have never thought of this solution...but finally I too managed to fix this weird issue with the help of your post.
Cheers!
However, here is a slightly less kludgy solution is to go to the properties for each SAN drive (M:, N:, O:, etc) -> Security -> Add your current username to the list, and Deny -> Full Control. Do this for each SAN drive and the installer will be forced to use the C: drive. Yay
Caleb
Obscure error while attempting to install SQL Server 2005 SP1
I successfully installed SQL Server 2005 SP1 on one PC. When I attempt to install it on a second PC, however, I get the following obscure error:
Unexpected Error Occurred
The following unexpected error occurred:
That's right, there's nothing else listed, other an OK button. D'oh! When I press the OK button, the following error report dialog box appears:
Hotfix.exe
A recently applied update, NULL, failed to install.
There are no pending updates that I'm aware of, as I just booted the PC. I sent the error report.
I notice on this particular PC that the SP1 install EXE is expanding/writing to an external SCSI drive; would that make a difference? I don't see a way to specify a different (i.e., internal ATA drive).
Any other ideas?
You need to look in the setup log files to track down the problem. They're located here:
%\Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
There's also a summary.txt file up one directory and it may point you to the right log file. If you have trouble interpreting the results, please post the errors here and we'll see if we can help you out.
Paul
|||Thanks. Before I delve further into the log file, I noticed that Summary.txt indicates everything is fine, although I don't understand the references to "Uninstall":
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Apr 14 00:07:10 2006
Machine : PC001
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Uninstall : Successful , Reboot required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQL.log
--
Machine : PC001
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQLSupport_1.log
--
Machine : PC001
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SqlWriter_1.log
--
Machine : PC001
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_MSXML6_1.log
--
Setup succeeded with the installation, inspect the log file completely for status on all the components.Time : Fri Apr 14 01:30:27 2006
I'm not sure why the first section says "Microsoft SQL Server 2005 Express Edition". I don't have the Express Edition installed on this PC, although I installed and uninstalled it a few months ago. Indeed, the Express Edition doesn't appear within the "Add or Remove Programs" applet.
I welcome your suggestions as to how to proceed.
|||If it's any comfort, you are not the only one with this error.
Installed fine the first time on my development server where it is a clean install of Windows 2003 and SQL 2005. However on the pc’s I have attempted to install on, where there is Visual Studio and Office installed it refuses to install.
I have tried on 3 other PC's and they all suffer the same way.
|||
Problem solved.
I took the time over the weekend ( I need to get a life) to build a clean OS install and install SQL 2005 developer edition and then install the service pack to see when and where it broke.
The issue seems to be associated with the fact that the SQL 2005 developer edition I was trying to upgrade was from the ISO image downloaded from the MSDN website. I uninstalled the ISO image and installed SQL from the MSDN subscription CD's and the service pack installs fine.
Can someone at Microsoft please confirm this is an issue!
|||
Interesting observation, Des; thanks. My install came from the ISO image downloaded from the MSDN website, also.
How do you know that simply uninstalling and re-installing didn't resolve the problem?
|||I actually reinstalled from the ISO image first with the same result.
I then went hunting through boxes of MSDN disks till I found the real disks, and reinstalled from the MSDN media. Once installed from the MSDN media the service pack installed first go.
|||We have ugraded one server with SP1 for SQL 2005 without any issues,but when we performed the same task on other server with the same sp1 setup,we encountered the problem which you experienced "The following unexpected error occurred" Both the servers are installed from the same ISO image of MSDN, Herby I attach the log of the hotfix which I executed.
05/26/2006 10:24:48.546 ================================================================================
05/26/2006 10:24:48.546 Hotfix package launched
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Local Computer:
05/26/2006 10:24:48.609 Target Details: SRC-R-AS10
05/26/2006 10:24:48.609 commonfilesdir = C:\Program Files\Common Files
05/26/2006 10:24:48.609 lcidsupportdir = s:\0596decce11fd6b46f501bbd4cfb\1033
05/26/2006 10:24:48.609 programfilesdir = C:\Program Files
05/26/2006 10:24:48.609 supportdir = \\SRC-R-AS10\s$\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 supportdirlocal = s:\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 windir = C:\WINDOWS
05/26/2006 10:24:48.609 winsysdir = C:\WINDOWS\system32
05/26/2006 10:24:48.609
05/26/2006 10:24:48.656 Enumerating applicable products for this patch
05/26/2006 10:24:53.046 The patch installation could not proceed due to unexpected errors
05/26/2006 10:24:53.046
05/26/2006 10:24:53.046 Product Status Summary:
05/26/2006 10:24:53.171 Hotfix package closed
We experience the same error while installing the hotfix AS2005-KB914595-x86-ENU.exe (this hotfix was installed on other server which upgraded successfully.)
Reinstalling is not a feasible option for our environment.Kindly suggest.
~Vishal
|||I received the same "A recently applied update, NULL, failed to install." error when attempting to install SP1 on SQL Server 2005 Enterprise version. As previously noted, I also uninstalled the ISO version from MSDN and re-installed from the MSDN DVD.
Following the reinstall, I attempted to run the individual hotfixes, starting with sql2005-kb918222-x86-enu.exe. Once again, I received the error.
Finally, I attempted to run the fixed patch noted in KB914595 and received a slightly different message but with the same, unsatisfactory results. The message has now changed to "Uninstallation of the 'NULL' update failed". Note that the installer chose to place the support directory on a SAN connection (F:). Could this be a lead toward a solution?
Here's the log file from the %WINDIR%\Hotfix folder:
08/05/2006 16:22:34.875 ================================================================================
08/05/2006 16:22:34.875 Hotfix package launched
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Local Computer:
08/05/2006 16:22:35.031 Target Details: EMERALD
08/05/2006 16:22:35.031 commonfilesdir = C:\Program Files\Common Files
08/05/2006 16:22:35.031 lcidsupportdir = f:\074fcbd1c0e3fd87748b2a9b748b9208\1033
08/05/2006 16:22:35.031 programfilesdir = C:\Program Files
08/05/2006 16:22:35.031 supportdir = \\EMERALD\f$\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 supportdirlocal = f:\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 windir = C:\WINDOWS
08/05/2006 16:22:35.031 winsysdir = C:\WINDOWS\system32
08/05/2006 16:22:35.031
08/05/2006 16:22:35.093 Enumerating applicable products for this patch
08/05/2006 16:22:36.625 The patch installation could not proceed due to unexpected errors
08/05/2006 16:22:36.625
08/05/2006 16:22:36.625 Product Status Summary:
08/05/2006 16:22:36.843 Hotfix package closed
I think I have a solution to the problem
After installing/uninstalling SQL Server several times and trying to install SP1, about a dozen or more times, I noticed that in the Hotfix log details (see my earlier posting) that the "lcidsupportdir", "supportdirlocal" and "supportdir" all referred to drive "F:". In the Hotfix log details posted by Vishal_LogicalCMG, these same values refer to drive "S:". On the system where SP-1 was failing, drive "F:" is connected to a SAN (I wonder if there's significance to the drive letter "S:" in Vishal's post?).
Since Hotfix.exe doesn't provide a parameter to specify these values, I guessed that Hotfix.exe simply looks for the drive with the most free space for its workspace. On my system, the SAN had a lot more space than the boot drive. I quickly whipped up a script that created a 1GB file and repeatedly made copies of it on drive F: until drive C: had more free space. (I know it's a hack, but I was desparate by now!)
You guessed it - Hotfix.exe now placed its workfiles on the root drive C: and SQL Server 2005 Enterprise version is running with SP-1 installed! It looks like Hotfix.exe doesn't like to work across a SAN.
Microsoft ... are you listening?
Dave
|||Thank you for help. I had the same problem with installing SP1 for SQL Server 2005. It was caused by running installation from USB harddrive. When I coppied SP1 installation to C: then SP1 and post-SP1 hotfixes installed successfully.|||Dave,
Thanks for your post. I had the same issue, but I was not using a SANS, i just had a second drive that had more free space than the C drive. When i filled up that drive the install worked just fine.
Gotta love the QA over at Microsoft sometimes...... DUH.
Thanks again.
|||An easy workaround is to set up a 1 kb Disk Quota on the Larger Drive, which will force the MSI installer to use the C: drive. :)|||Thanks a million Dave! Genious Stuff
I would have never thought of this solution...but finally I too managed to fix this weird issue with the help of your post.
Cheers!
|||The disk quote workaround did not work for me....
However, here is a slightly less kludgy solution is to go to the properties for each SAN drive (M:, N:, O:, etc) -> Security -> Add
your current username to the list, and Deny -> Full Control. Do this for
each SAN drive and the installer will be forced to use the C: drive. Yay
Caleb
Obscure error while attempting to install SQL Server 2005 SP1
I successfully installed SQL Server 2005 SP1 on one PC. When I attempt to install it on a second PC, however, I get the following obscure error:
Unexpected Error Occurred
The following unexpected error occurred:
That's right, there's nothing else listed, other an OK button. D'oh! When I press the OK button, the following error report dialog box appears:
Hotfix.exe
A recently applied update, NULL, failed to install.
There are no pending updates that I'm aware of, as I just booted the PC. I sent the error report.
I notice on this particular PC that the SP1 install EXE is expanding/writing to an external SCSI drive; would that make a difference? I don't see a way to specify a different (i.e., internal ATA drive).
Any other ideas?
You need to look in the setup log files to track down the problem. They're located here:
%\Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
There's also a summary.txt file up one directory and it may point you to the right log file. If you have trouble interpreting the results, please post the errors here and we'll see if we can help you out.
Paul
|||Thanks. Before I delve further into the log file, I noticed that Summary.txt indicates everything is fine, although I don't understand the references to "Uninstall":
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Apr 14 00:07:10 2006
Machine : PC001
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Uninstall : Successful , Reboot required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQL.log
--
Machine : PC001
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQLSupport_1.log
--
Machine : PC001
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SqlWriter_1.log
--
Machine : PC001
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_MSXML6_1.log
--
Setup succeeded with the installation, inspect the log file completely for status on all the components.Time : Fri Apr 14 01:30:27 2006
I'm not sure why the first section says "Microsoft SQL Server 2005 Express Edition". I don't have the Express Edition installed on this PC, although I installed and uninstalled it a few months ago. Indeed, the Express Edition doesn't appear within the "Add or Remove Programs" applet.
I welcome your suggestions as to how to proceed.
|||If it's any comfort, you are not the only one with this error.
Installed fine the first time on my development server where it is a clean install of Windows 2003 and SQL 2005. However on the pc’s I have attempted to install on, where there is Visual Studio and Office installed it refuses to install.
I have tried on 3 other PC's and they all suffer the same way.
|||
Problem solved.
I took the time over the weekend ( I need to get a life) to build a clean OS install and install SQL 2005 developer edition and then install the service pack to see when and where it broke.
The issue seems to be associated with the fact that the SQL 2005 developer edition I was trying to upgrade was from the ISO image downloaded from the MSDN website. I uninstalled the ISO image and installed SQL from the MSDN subscription CD's and the service pack installs fine.
Can someone at Microsoft please confirm this is an issue!
|||
Interesting observation, Des; thanks. My install came from the ISO image downloaded from the MSDN website, also.
How do you know that simply uninstalling and re-installing didn't resolve the problem?
|||I actually reinstalled from the ISO image first with the same result.
I then went hunting through boxes of MSDN disks till I found the real disks, and reinstalled from the MSDN media. Once installed from the MSDN media the service pack installed first go.
|||We have ugraded one server with SP1 for SQL 2005 without any issues,but when we performed the same task on other server with the same sp1 setup,we encountered the problem which you experienced "The following unexpected error occurred" Both the servers are installed from the same ISO image of MSDN, Herby I attach the log of the hotfix which I executed.
05/26/2006 10:24:48.546 ================================================================================
05/26/2006 10:24:48.546 Hotfix package launched
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Local Computer:
05/26/2006 10:24:48.609 Target Details: SRC-R-AS10
05/26/2006 10:24:48.609 commonfilesdir = C:\Program Files\Common Files
05/26/2006 10:24:48.609 lcidsupportdir = s:\0596decce11fd6b46f501bbd4cfb\1033
05/26/2006 10:24:48.609 programfilesdir = C:\Program Files
05/26/2006 10:24:48.609 supportdir = \\SRC-R-AS10\s$\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 supportdirlocal = s:\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 windir = C:\WINDOWS
05/26/2006 10:24:48.609 winsysdir = C:\WINDOWS\system32
05/26/2006 10:24:48.609
05/26/2006 10:24:48.656 Enumerating applicable products for this patch
05/26/2006 10:24:53.046 The patch installation could not proceed due to unexpected errors
05/26/2006 10:24:53.046
05/26/2006 10:24:53.046 Product Status Summary:
05/26/2006 10:24:53.171 Hotfix package closed
We experience the same error while installing the hotfix AS2005-KB914595-x86-ENU.exe (this hotfix was installed on other server which upgraded successfully.)
Reinstalling is not a feasible option for our environment.Kindly suggest.
~Vishal
|||I received the same "A recently applied update, NULL, failed to install." error when attempting to install SP1 on SQL Server 2005 Enterprise version. As previously noted, I also uninstalled the ISO version from MSDN and re-installed from the MSDN DVD.
Following the reinstall, I attempted to run the individual hotfixes, starting with sql2005-kb918222-x86-enu.exe. Once again, I received the error.
Finally, I attempted to run the fixed patch noted in KB914595 and received a slightly different message but with the same, unsatisfactory results. The message has now changed to "Uninstallation of the 'NULL' update failed". Note that the installer chose to place the support directory on a SAN connection (F:). Could this be a lead toward a solution?
Here's the log file from the %WINDIR%\Hotfix folder:
08/05/2006 16:22:34.875 ================================================================================
08/05/2006 16:22:34.875 Hotfix package launched
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Local Computer:
08/05/2006 16:22:35.031 Target Details: EMERALD
08/05/2006 16:22:35.031 commonfilesdir = C:\Program Files\Common Files
08/05/2006 16:22:35.031 lcidsupportdir = f:\074fcbd1c0e3fd87748b2a9b748b9208\1033
08/05/2006 16:22:35.031 programfilesdir = C:\Program Files
08/05/2006 16:22:35.031 supportdir = \\EMERALD\f$\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 supportdirlocal = f:\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 windir = C:\WINDOWS
08/05/2006 16:22:35.031 winsysdir = C:\WINDOWS\system32
08/05/2006 16:22:35.031
08/05/2006 16:22:35.093 Enumerating applicable products for this patch
08/05/2006 16:22:36.625 The patch installation could not proceed due to unexpected errors
08/05/2006 16:22:36.625
08/05/2006 16:22:36.625 Product Status Summary:
08/05/2006 16:22:36.843 Hotfix package closed
I think I have a solution to the problem
After installing/uninstalling SQL Server several times and trying to install SP1, about a dozen or more times, I noticed that in the Hotfix log details (see my earlier posting) that the "lcidsupportdir", "supportdirlocal" and "supportdir" all referred to drive "F:". In the Hotfix log details posted by Vishal_LogicalCMG, these same values refer to drive "S:". On the system where SP-1 was failing, drive "F:" is connected to a SAN (I wonder if there's significance to the drive letter "S:" in Vishal's post?).
Since Hotfix.exe doesn't provide a parameter to specify these values, I guessed that Hotfix.exe simply looks for the drive with the most free space for its workspace. On my system, the SAN had a lot more space than the boot drive. I quickly whipped up a script that created a 1GB file and repeatedly made copies of it on drive F: until drive C: had more free space. (I know it's a hack, but I was desparate by now!)
You guessed it - Hotfix.exe now placed its workfiles on the root drive C: and SQL Server 2005 Enterprise version is running with SP-1 installed! It looks like Hotfix.exe doesn't like to work across a SAN.
Microsoft ... are you listening?
Dave
|||Thank you for help. I had the same problem with installing SP1 for SQL Server 2005. It was caused by running installation from USB harddrive. When I coppied SP1 installation to C: then SP1 and post-SP1 hotfixes installed successfully.|||Dave,
Thanks for your post. I had the same issue, but I was not using a SANS, i just had a second drive that had more free space than the C drive. When i filled up that drive the install worked just fine.
Gotta love the QA over at Microsoft sometimes...... DUH.
Thanks again.
|||An easy workaround is to set up a 1 kb Disk Quota on the Larger Drive, which will force the MSI installer to use the C: drive. :)|||Thanks a million Dave! Genious Stuff
I would have never thought of this solution...but finally I too managed to fix this weird issue with the help of your post.
Cheers!
|||The disk quote workaround did not work for me....
However, here is a slightly less kludgy solution is to go to the properties for each SAN drive (M:, N:, O:, etc) -> Security -> Add
your current username to the list, and Deny -> Full Control. Do this for
each SAN drive and the installer will be forced to use the C: drive. Yay
Caleb
Obscure error while attempting to install SQL Server 2005 SP1
I successfully installed SQL Server 2005 SP1 on one PC. When I attempt to install it on a second PC, however, I get the following obscure error:
Unexpected Error Occurred
The following unexpected error occurred:
That's right, there's nothing else listed, other an OK button. D'oh! When I press the OK button, the following error report dialog box appears:
Hotfix.exe
A recently applied update, NULL, failed to install.
There are no pending updates that I'm aware of, as I just booted the PC. I sent the error report.
I notice on this particular PC that the SP1 install EXE is expanding/writing to an external SCSI drive; would that make a difference? I don't see a way to specify a different (i.e., internal ATA drive).
Any other ideas?
You need to look in the setup log files to track down the problem. They're located here:
%\Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
There's also a summary.txt file up one directory and it may point you to the right log file. If you have trouble interpreting the results, please post the errors here and we'll see if we can help you out.
Paul
|||Thanks. Before I delve further into the log file, I noticed that Summary.txt indicates everything is fine, although I don't understand the references to "Uninstall":
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Apr 14 00:07:10 2006
Machine : PC001
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Uninstall : Successful , Reboot required
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQL.log
--
Machine : PC001
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SQLSupport_1.log
--
Machine : PC001
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_SqlWriter_1.log
--
Machine : PC001
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_PC001_MSXML6_1.log
--
Setup succeeded with the installation, inspect the log file completely for status on all the components.Time : Fri Apr 14 01:30:27 2006
I'm not sure why the first section says "Microsoft SQL Server 2005 Express Edition". I don't have the Express Edition installed on this PC, although I installed and uninstalled it a few months ago. Indeed, the Express Edition doesn't appear within the "Add or Remove Programs" applet.
I welcome your suggestions as to how to proceed.
|||If it's any comfort, you are not the only one with this error.
Installed fine the first time on my development server where it is a clean install of Windows 2003 and SQL 2005. However on the pc’s I have attempted to install on, where there is Visual Studio and Office installed it refuses to install.
I have tried on 3 other PC's and they all suffer the same way.
|||
Problem solved.
I took the time over the weekend ( I need to get a life) to build a clean OS install and install SQL 2005 developer edition and then install the service pack to see when and where it broke.
The issue seems to be associated with the fact that the SQL 2005 developer edition I was trying to upgrade was from the ISO image downloaded from the MSDN website. I uninstalled the ISO image and installed SQL from the MSDN subscription CD's and the service pack installs fine.
Can someone at Microsoft please confirm this is an issue!
|||
Interesting observation, Des; thanks. My install came from the ISO image downloaded from the MSDN website, also.
How do you know that simply uninstalling and re-installing didn't resolve the problem?
|||I actually reinstalled from the ISO image first with the same result.
I then went hunting through boxes of MSDN disks till I found the real disks, and reinstalled from the MSDN media. Once installed from the MSDN media the service pack installed first go.
|||We have ugraded one server with SP1 for SQL 2005 without any issues,but when we performed the same task on other server with the same sp1 setup,we encountered the problem which you experienced "The following unexpected error occurred" Both the servers are installed from the same ISO image of MSDN, Herby I attach the log of the hotfix which I executed.
05/26/2006 10:24:48.546 ================================================================================
05/26/2006 10:24:48.546 Hotfix package launched
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.546 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.546 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
05/26/2006 10:24:48.609 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
05/26/2006 10:24:48.609 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
05/26/2006 10:24:48.609 Local Computer:
05/26/2006 10:24:48.609 Target Details: SRC-R-AS10
05/26/2006 10:24:48.609 commonfilesdir = C:\Program Files\Common Files
05/26/2006 10:24:48.609 lcidsupportdir = s:\0596decce11fd6b46f501bbd4cfb\1033
05/26/2006 10:24:48.609 programfilesdir = C:\Program Files
05/26/2006 10:24:48.609 supportdir = \\SRC-R-AS10\s$\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 supportdirlocal = s:\0596decce11fd6b46f501bbd4cfb
05/26/2006 10:24:48.609 windir = C:\WINDOWS
05/26/2006 10:24:48.609 winsysdir = C:\WINDOWS\system32
05/26/2006 10:24:48.609
05/26/2006 10:24:48.656 Enumerating applicable products for this patch
05/26/2006 10:24:53.046 The patch installation could not proceed due to unexpected errors
05/26/2006 10:24:53.046
05/26/2006 10:24:53.046 Product Status Summary:
05/26/2006 10:24:53.171 Hotfix package closed
We experience the same error while installing the hotfix AS2005-KB914595-x86-ENU.exe (this hotfix was installed on other server which upgraded successfully.)
Reinstalling is not a feasible option for our environment.Kindly suggest.
~Vishal
|||I received the same "A recently applied update, NULL, failed to install." error when attempting to install SP1 on SQL Server 2005 Enterprise version. As previously noted, I also uninstalled the ISO version from MSDN and re-installed from the MSDN DVD.
Following the reinstall, I attempted to run the individual hotfixes, starting with sql2005-kb918222-x86-enu.exe. Once again, I received the error.
Finally, I attempted to run the fixed patch noted in KB914595 and received a slightly different message but with the same, unsatisfactory results. The message has now changed to "Uninstallation of the 'NULL' update failed". Note that the installer chose to place the support directory on a SAN connection (F:). Could this be a lead toward a solution?
Here's the log file from the %WINDIR%\Hotfix folder:
08/05/2006 16:22:34.875 ================================================================================
08/05/2006 16:22:34.875 Hotfix package launched
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:34.890 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:34.890 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
08/05/2006 16:22:35.031 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
08/05/2006 16:22:35.031 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
08/05/2006 16:22:35.031 Local Computer:
08/05/2006 16:22:35.031 Target Details: EMERALD
08/05/2006 16:22:35.031 commonfilesdir = C:\Program Files\Common Files
08/05/2006 16:22:35.031 lcidsupportdir = f:\074fcbd1c0e3fd87748b2a9b748b9208\1033
08/05/2006 16:22:35.031 programfilesdir = C:\Program Files
08/05/2006 16:22:35.031 supportdir = \\EMERALD\f$\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 supportdirlocal = f:\074fcbd1c0e3fd87748b2a9b748b9208
08/05/2006 16:22:35.031 windir = C:\WINDOWS
08/05/2006 16:22:35.031 winsysdir = C:\WINDOWS\system32
08/05/2006 16:22:35.031
08/05/2006 16:22:35.093 Enumerating applicable products for this patch
08/05/2006 16:22:36.625 The patch installation could not proceed due to unexpected errors
08/05/2006 16:22:36.625
08/05/2006 16:22:36.625 Product Status Summary:
08/05/2006 16:22:36.843 Hotfix package closed
I think I have a solution to the problem
After installing/uninstalling SQL Server several times and trying to install SP1, about a dozen or more times, I noticed that in the Hotfix log details (see my earlier posting) that the "lcidsupportdir", "supportdirlocal" and "supportdir" all referred to drive "F:". In the Hotfix log details posted by Vishal_LogicalCMG, these same values refer to drive "S:". On the system where SP-1 was failing, drive "F:" is connected to a SAN (I wonder if there's significance to the drive letter "S:" in Vishal's post?).
Since Hotfix.exe doesn't provide a parameter to specify these values, I guessed that Hotfix.exe simply looks for the drive with the most free space for its workspace. On my system, the SAN had a lot more space than the boot drive. I quickly whipped up a script that created a 1GB file and repeatedly made copies of it on drive F: until drive C: had more free space. (I know it's a hack, but I was desparate by now!)
You guessed it - Hotfix.exe now placed its workfiles on the root drive C: and SQL Server 2005 Enterprise version is running with SP-1 installed! It looks like Hotfix.exe doesn't like to work across a SAN.
Microsoft ... are you listening?
Dave
|||Thank you for help. I had the same problem with installing SP1 for SQL Server 2005. It was caused by running installation from USB harddrive. When I coppied SP1 installation to C: then SP1 and post-SP1 hotfixes installed successfully.|||Dave,
Thanks for your post. I had the same issue, but I was not using a SANS, i just had a second drive that had more free space than the C drive. When i filled up that drive the install worked just fine.
Gotta love the QA over at Microsoft sometimes...... DUH.
Thanks again.
|||An easy workaround is to set up a 1 kb Disk Quota on the Larger Drive, which will force the MSI installer to use the C: drive. :)|||Thanks a million Dave! Genious Stuff
I would have never thought of this solution...but finally I too managed to fix this weird issue with the help of your post.
Cheers!
However, here is a slightly less kludgy solution is to go to the properties for each SAN drive (M:, N:, O:, etc) -> Security -> Add your current username to the list, and Deny -> Full Control. Do this for each SAN drive and the installer will be forced to use the C: drive. Yay
Caleb
Subscribe to:
Posts (Atom)