Hiya folks,
I'm a newbie at this, so forgive the ignorance that I may display!
I have installed a software package on my system that installs MSDE through
merge modules contained in its MSI. I have several workstations that
connect. Unfortunately, with SP2 coming down the pipe for windows xp, i
have to do lots of fancy stuff to make sure they still connect (it uses
named pipes tcp/ip). The solution according to microsoft is to install SP3
for sql...i've downloaded the MSDE version of the upgrade, and attempted to
install for several hours with no luck.
First, it said i required a strong password, which i supplised in the
setup.ini:
[options]
sapassword="mypassword"
Things started to load, and then the installer quit. Confused, I started it
again. Now the installer is giving me '
the instance name specified is invalid'
Ok, so i go back to the setup.ini and add a line
[options]
sapassword="mypassword"
instancename="liveddm"
and STILL, i get the invalid instance name error message. No matter what I
seem to try, it is telling me i have an invalid instance name; if i use
enterprise manager, i can clearly see my instance and browse the attached
database. I've also tried instancename="computername\liveddm" with no luck.
Any help would be greatly appreciated.
Thanks!
Sheldon
sheldon@.REMOVETHISthedoctorcompany.com
Sheldon Purkiss wrote:
> Hiya folks,
> I'm a newbie at this, so forgive the ignorance that I may display!
> I have installed a software package on my system that installs MSDE through
> merge modules contained in its MSI. I have several workstations that
> connect. Unfortunately, with SP2 coming down the pipe for windows xp, i
> have to do lots of fancy stuff to make sure they still connect (it uses
> named pipes tcp/ip). The solution according to microsoft is to install SP3
> for sql...i've downloaded the MSDE version of the upgrade, and attempted to
> install for several hours with no luck.
> First, it said i required a strong password, which i supplised in the
> setup.ini:
> [options]
> sapassword="mypassword"
> Things started to load, and then the installer quit. Confused, I started it
> again. Now the installer is giving me '
> the instance name specified is invalid'
> Ok, so i go back to the setup.ini and add a line
> [options]
> sapassword="mypassword"
> instancename="liveddm"
> and STILL, i get the invalid instance name error message. No matter what I
> seem to try, it is telling me i have an invalid instance name; if i use
> enterprise manager, i can clearly see my instance and browse the attached
> database. I've also tried instancename="computername\liveddm" with no luck.
> Any help would be greatly appreciated.
> Thanks!
> Sheldon
> sheldon@.REMOVETHISthedoctorcompany.com
>
>
>
Hi Sheldon
Unfortunately, I believe that if your software vendor has installed MSDE
using merge modules from within their own MSI they will need to supply
you with the patch package themselves.
See http://www.microsoft.com/sql/downloads/2000/sp3.asp
Tony
Showing posts with label package. Show all posts
Showing posts with label package. Show all posts
Friday, March 30, 2012
Installing MSDE (VB.NET)
Hi,
I need to package and deploy my MSDE database with my application. How do I
do this? It needs to deploy, install, and I need to also install tables,
users, user rights and also possibly some sample data.
I can do an unattended install, but do I have to write a seperate program or
use osql/isql to run batch file/sql scripts to update the database?
Surely there's an automated method to "click-and-install"...?
Liddle Feesh
*fap fap fap fap*
<>< <>< <>< <>< ><>
<>< <>< <>< <>< <>< <><
My friend, there is no elegant way to do this.
Microsoft offers merge modules that will handle the installation for you. You can then use a CustomAction to attach a database or run SQL statementts to create a database. This isn't recommended because now YOU become responsible for creating a patch file
to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.
What I have ended up doing is programmatically shelling out to call the setup.exe program that is included with MSDE. I have created a program that looks similar to the Visual Studio .NET install where users can first click on a link to launch the SQL Ser
ver 2000 MSDE install, then install my application.
Microsoft has also created a gimpy MSDE/.NET Framework bootstrapper, but it is far from being stable. I personally think it's a piece of junk and wouldn't recommend it. *Supposedly*, if the next version of Visual Studio EVER ships, a generic bootstrapper
is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.
I recommend shelling out to the setup.exe program provided with MSDE. Good luck.
Rob Reagan
"Liddle Feesh" wrote:
> Hi,
> I need to package and deploy my MSDE database with my application. How do I
> do this? It needs to deploy, install, and I need to also install tables,
> users, user rights and also possibly some sample data.
> I can do an unattended install, but do I have to write a seperate program or
> use osql/isql to run batch file/sql scripts to update the database?
> Surely there's an automated method to "click-and-install"...?
>
> --
> Liddle Feesh
> *fap fap fap fap*
> <>< <>< <>< <>< ><>
> <>< <>< <>< <>< <>< <><
>
>
|||Hi Rob,
I have been using the MSDE bootstrapper and have had quiet a few issues with it, like the installation just hangs many times, the MSDE instance needs to be reinstalled even if it is installed (a confirmed bug my Microsoft here), etc.. you mentioned you ar
e shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.
Thanks
dev
"Rob Reagan" wrote:
> My friend, there is no elegant way to do this.
> Microsoft offers merge modules that will handle the installation for you. You can then use a CustomAction to attach a database or run SQL statementts to create a database. This isn't recommended because now YOU become responsible for creating a patch fi
le to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.
> What I have ended up doing is programmatically shelling out to call the setup.exe program that is included with MSDE. I have created a program that looks similar to the Visual Studio .NET install where users can first click on a link to launch the SQL S
erver 2000 MSDE install, then install my application.
> Microsoft has also created a gimpy MSDE/.NET Framework bootstrapper, but it is far from being stable. I personally think it's a piece of junk and wouldn't recommend it. *Supposedly*, if the next version of Visual Studio EVER ships, a generic bootstrappe
r is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
> I recommend shelling out to the setup.exe program provided with MSDE. Good luck.
> Rob Reagan
> "Liddle Feesh" wrote:
|||Since I am using this as a remote database over the network, I'm setting DISABLENETWORKPROTOCOLS=0. I'm also setting the SAPWD, INSTANCENAME, and SECURITYMODE parameters.
Be forewarned that the MSDE installer is a great example of the half-baked software that Microsoft inflicts on the public. The uninstaller leaves garbage behind. While developing, you're going to have to do alot of removal of orphaned files and registry k
eys by hand before you can attempt a reinstall for the same named instance.
Be very careful when cleaning out your registry from orphaned MSDE keys. I zapped a few that I shouldn't have and was unable to reinstall MSDE, period. I've got to reformat my drive and reinstall Windows.
Rob
"dev_kh" wrote:
> Hi Rob,
> I have been using the MSDE bootstrapper and have had quiet a few issues with it, like the installation just hangs many times, the MSDE instance needs to be reinstalled even if it is installed (a confirmed bug my Microsoft here), etc.. you mentioned you
are shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.[vbcol=seagreen]
> Thanks
> dev
> "Rob Reagan" wrote:
file to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.[vbcol=seagreen]
Server 2000 MSDE install, then install my application.[vbcol=seagreen]
per is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
|||Oh My Goodness, I also had to manually delete the registry keys many times but no formatting so far. Thanks for your reply though. I was wondering more in lines with figuring out whether the MSDE installation went fine or not when you shell it out. Als
o do you do any logging of the MSDE installation..
Thanks again
"Rob Reagan" wrote:
> Since I am using this as a remote database over the network, I'm setting DISABLENETWORKPROTOCOLS=0. I'm also setting the SAPWD, INSTANCENAME, and SECURITYMODE parameters.
> Be forewarned that the MSDE installer is a great example of the half-baked software that Microsoft inflicts on the public. The uninstaller leaves garbage behind. While developing, you're going to have to do alot of removal of orphaned files and registry
keys by hand before you can attempt a reinstall for the same named instance.[vbcol=seagreen]
> Be very careful when cleaning out your registry from orphaned MSDE keys. I zapped a few that I shouldn't have and was unable to reinstall MSDE, period. I've got to reformat my drive and reinstall Windows.
> Rob
> "dev_kh" wrote:
u are shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.[vbcol=seagreen]
h file to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.[vbcol=seagreen]
QL Server 2000 MSDE install, then install my application.[vbcol=seagreen]
apper is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
|||I have had good luck shelling the setup.exe program. My only complaint there is that the uninstaller is so sloppy and leaves behind a bunch of keys and files. I do not log in my production program, only in my test environment. I have considered writing my
own custom uninstaller that shells to the windows uninstaller, then cleans up keys and files afterwards. The only disadvantage is that the user could bypass my customer uninstaller (accesible through the programs menu) and use the one in Add\Remove Progr
ams.
Rob
"dev_kh" wrote:
> Oh My Goodness, I also had to manually delete the registry keys many times but no formatting so far. Thanks for your reply though. I was wondering more in lines with figuring out whether the MSDE installation went fine or not when you shell it out. A
lso do you do any logging of the MSDE installation..[vbcol=seagreen]
> Thanks again
> "Rob Reagan" wrote:
ry keys by hand before you can attempt a reinstall for the same named instance.[vbcol=seagreen]
you are shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.[vbcol=seagreen]
tch file to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.[vbcol=seagreen]
SQL Server 2000 MSDE install, then install my application.[vbcol=seagreen]
trapper is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
|||Hi Rob,
Cheers for the reply (and the other guys too!) - I've heard Microsoft
released an MSDE Installer SDK in December 2003... might be worth a look
at?
It's pretty late and I've just got in - so I'll have to look at this
tomorrow!
cya later, chaps!
Liddle Feesh
*fap fap fap fap*
<>< <>< <>< <>< ><>
<>< <>< <>< <>< <>< <><
I need to package and deploy my MSDE database with my application. How do I
do this? It needs to deploy, install, and I need to also install tables,
users, user rights and also possibly some sample data.
I can do an unattended install, but do I have to write a seperate program or
use osql/isql to run batch file/sql scripts to update the database?
Surely there's an automated method to "click-and-install"...?
Liddle Feesh
*fap fap fap fap*
<>< <>< <>< <>< ><>
<>< <>< <>< <>< <>< <><
My friend, there is no elegant way to do this.
Microsoft offers merge modules that will handle the installation for you. You can then use a CustomAction to attach a database or run SQL statementts to create a database. This isn't recommended because now YOU become responsible for creating a patch file
to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.
What I have ended up doing is programmatically shelling out to call the setup.exe program that is included with MSDE. I have created a program that looks similar to the Visual Studio .NET install where users can first click on a link to launch the SQL Ser
ver 2000 MSDE install, then install my application.
Microsoft has also created a gimpy MSDE/.NET Framework bootstrapper, but it is far from being stable. I personally think it's a piece of junk and wouldn't recommend it. *Supposedly*, if the next version of Visual Studio EVER ships, a generic bootstrapper
is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.
I recommend shelling out to the setup.exe program provided with MSDE. Good luck.
Rob Reagan
"Liddle Feesh" wrote:
> Hi,
> I need to package and deploy my MSDE database with my application. How do I
> do this? It needs to deploy, install, and I need to also install tables,
> users, user rights and also possibly some sample data.
> I can do an unattended install, but do I have to write a seperate program or
> use osql/isql to run batch file/sql scripts to update the database?
> Surely there's an automated method to "click-and-install"...?
>
> --
> Liddle Feesh
> *fap fap fap fap*
> <>< <>< <>< <>< ><>
> <>< <>< <>< <>< <>< <><
>
>
|||Hi Rob,
I have been using the MSDE bootstrapper and have had quiet a few issues with it, like the installation just hangs many times, the MSDE instance needs to be reinstalled even if it is installed (a confirmed bug my Microsoft here), etc.. you mentioned you ar
e shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.
Thanks
dev
"Rob Reagan" wrote:
> My friend, there is no elegant way to do this.
> Microsoft offers merge modules that will handle the installation for you. You can then use a CustomAction to attach a database or run SQL statementts to create a database. This isn't recommended because now YOU become responsible for creating a patch fi
le to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.
> What I have ended up doing is programmatically shelling out to call the setup.exe program that is included with MSDE. I have created a program that looks similar to the Visual Studio .NET install where users can first click on a link to launch the SQL S
erver 2000 MSDE install, then install my application.
> Microsoft has also created a gimpy MSDE/.NET Framework bootstrapper, but it is far from being stable. I personally think it's a piece of junk and wouldn't recommend it. *Supposedly*, if the next version of Visual Studio EVER ships, a generic bootstrappe
r is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
> I recommend shelling out to the setup.exe program provided with MSDE. Good luck.
> Rob Reagan
> "Liddle Feesh" wrote:
|||Since I am using this as a remote database over the network, I'm setting DISABLENETWORKPROTOCOLS=0. I'm also setting the SAPWD, INSTANCENAME, and SECURITYMODE parameters.
Be forewarned that the MSDE installer is a great example of the half-baked software that Microsoft inflicts on the public. The uninstaller leaves garbage behind. While developing, you're going to have to do alot of removal of orphaned files and registry k
eys by hand before you can attempt a reinstall for the same named instance.
Be very careful when cleaning out your registry from orphaned MSDE keys. I zapped a few that I shouldn't have and was unable to reinstall MSDE, period. I've got to reformat my drive and reinstall Windows.
Rob
"dev_kh" wrote:
> Hi Rob,
> I have been using the MSDE bootstrapper and have had quiet a few issues with it, like the installation just hangs many times, the MSDE instance needs to be reinstalled even if it is installed (a confirmed bug my Microsoft here), etc.. you mentioned you
are shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.[vbcol=seagreen]
> Thanks
> dev
> "Rob Reagan" wrote:
file to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.[vbcol=seagreen]
Server 2000 MSDE install, then install my application.[vbcol=seagreen]
per is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
|||Oh My Goodness, I also had to manually delete the registry keys many times but no formatting so far. Thanks for your reply though. I was wondering more in lines with figuring out whether the MSDE installation went fine or not when you shell it out. Als
o do you do any logging of the MSDE installation..
Thanks again
"Rob Reagan" wrote:
> Since I am using this as a remote database over the network, I'm setting DISABLENETWORKPROTOCOLS=0. I'm also setting the SAPWD, INSTANCENAME, and SECURITYMODE parameters.
> Be forewarned that the MSDE installer is a great example of the half-baked software that Microsoft inflicts on the public. The uninstaller leaves garbage behind. While developing, you're going to have to do alot of removal of orphaned files and registry
keys by hand before you can attempt a reinstall for the same named instance.[vbcol=seagreen]
> Be very careful when cleaning out your registry from orphaned MSDE keys. I zapped a few that I shouldn't have and was unable to reinstall MSDE, period. I've got to reformat my drive and reinstall Windows.
> Rob
> "dev_kh" wrote:
u are shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.[vbcol=seagreen]
h file to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.[vbcol=seagreen]
QL Server 2000 MSDE install, then install my application.[vbcol=seagreen]
apper is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
|||I have had good luck shelling the setup.exe program. My only complaint there is that the uninstaller is so sloppy and leaves behind a bunch of keys and files. I do not log in my production program, only in my test environment. I have considered writing my
own custom uninstaller that shells to the windows uninstaller, then cleans up keys and files afterwards. The only disadvantage is that the user could bypass my customer uninstaller (accesible through the programs menu) and use the one in Add\Remove Progr
ams.
Rob
"dev_kh" wrote:
> Oh My Goodness, I also had to manually delete the registry keys many times but no formatting so far. Thanks for your reply though. I was wondering more in lines with figuring out whether the MSDE installation went fine or not when you shell it out. A
lso do you do any logging of the MSDE installation..[vbcol=seagreen]
> Thanks again
> "Rob Reagan" wrote:
ry keys by hand before you can attempt a reinstall for the same named instance.[vbcol=seagreen]
you are shelling out the exe yourself. I was just wondering what all parameters are you taking care of.. I mean In general what pointers/advise will you give to anyone who wants to do the same thing.[vbcol=seagreen]
tch file to patch the millions of security holes in MSDE. MSDE also uninstalls with your program under this scenario.[vbcol=seagreen]
SQL Server 2000 MSDE install, then install my application.[vbcol=seagreen]
trapper is supposed to be included that will allow chained .MSI installations. But until then, we're out of luck.[vbcol=seagreen]
|||Hi Rob,
Cheers for the reply (and the other guys too!) - I've heard Microsoft
released an MSDE Installer SDK in December 2003... might be worth a look
at?
It's pretty late and I've just got in - so I'll have to look at this
tomorrow!
cya later, chaps!
Liddle Feesh
*fap fap fap fap*
<>< <>< <>< <>< ><>
<>< <>< <>< <>< <>< <><
Monday, March 26, 2012
Installing Database
Hi,
My client is US based. Now I want to send them the database script for the package installation. Client does'nt have any technical people. So all I have to do it remotely from India. So could any one guide me on this?
thnxDuplicate post. Has been answered in other thread.|||you can send me a check and your worries would all be gonesql
My client is US based. Now I want to send them the database script for the package installation. Client does'nt have any technical people. So all I have to do it remotely from India. So could any one guide me on this?
thnxDuplicate post. Has been answered in other thread.|||you can send me a check and your worries would all be gonesql
Installing Database
Hi,
My client is US based. Now I want to send them the database script for the package installation. Client does'nt have any technical people. So all I have to do it remotely from India. So could any one guide me on this?
thnxWhat exactly is the problem. Either you can ask them to install by sending the database scripts, or ask them to install a remote server and connect from India remotely. In case of remote connection, they have to open up their server ports to skip the firewall. Then you can connect from India and do everything yourself.|||Could you please come up with a more clear picture, on remote connection and opening the port................?
thnx|||You can install MS Remote Desktop Connection software in your computer and connect to the sql server remotely. For that, you have to ask your client to open you the sql server, http and ftp ports to you.|||They would be crazy to open up ports on their SQL Servers though for you to work on it remotely from India. Just make a backup of a database with only the data needed. They can just restore the database on their SQL Server as part of the installation process. The alternative is to give them a script that creates the database, users, tables, stored procs, etc. and inserts the data needed. That's more prone to error though and harder to troubleshoot.
This is pretty standard practice and you should probably know this if you are going to be distributing commercial applications that utilize SQL Server. You might want to hire a DBA or look at consulting services for your company.|||yup, hire me!
My client is US based. Now I want to send them the database script for the package installation. Client does'nt have any technical people. So all I have to do it remotely from India. So could any one guide me on this?
thnxWhat exactly is the problem. Either you can ask them to install by sending the database scripts, or ask them to install a remote server and connect from India remotely. In case of remote connection, they have to open up their server ports to skip the firewall. Then you can connect from India and do everything yourself.|||Could you please come up with a more clear picture, on remote connection and opening the port................?
thnx|||You can install MS Remote Desktop Connection software in your computer and connect to the sql server remotely. For that, you have to ask your client to open you the sql server, http and ftp ports to you.|||They would be crazy to open up ports on their SQL Servers though for you to work on it remotely from India. Just make a backup of a database with only the data needed. They can just restore the database on their SQL Server as part of the installation process. The alternative is to give them a script that creates the database, users, tables, stored procs, etc. and inserts the data needed. That's more prone to error though and harder to troubleshoot.
This is pretty standard practice and you should probably know this if you are going to be distributing commercial applications that utilize SQL Server. You might want to hire a DBA or look at consulting services for your company.|||yup, hire me!
Installing and Uninstalling Express Edition
Hi guys,
I'm trying to create a all-in-one installation package for my application which make use of the SQL 2005 Express edition. It seems that there's no way to roll my application MSI installation with the database engine, the only ways around this problem is to use a bootstrap exe to launch the sql setup before or after my main application's MSI. This works fine during installation and I have modified the original .NET framework bootstrapper to do just that.
The problem comes when uninstalling my application. Since the uninstall process is all done through the MSI engine, how would I take the sql instance with me during my application's uninstall? Since the sql engine is also based on MSI technology, I won't be able to do that during the removal step of my application's MSI, right? Any one know any "clean" ways around that? Besides not letting users uninstall my application directly from Add/Remove program and force them to call another exe simular to my installation bootstrap?
I'm considering to use 3rd party tools like InstallShields, but even them are recommending people to stay with the MSI technology which is where the problem is. I'm running out of ideas really fast...
Thanks in advance!
William
Hi,
Since my initial posting, I've been working on the command to uninstall a named instance of SQL Server 2005. I though it would help once I get my problem above solved, as it seems to be the next logical step.
It seems that from MSDN (http://support.microsoft.com/default.aspx/kb/909967), there isn't a way to automate this process neither. The command ARPWrapper.exe don't have (or I couldn't fine) parameter to specify the named instance I'm trying to remove. The switch "/REMOVE" just brings up a window letting user choose their instance to remove. Anyone knows if such a way exists?
As I've said before, I'm trying to package my .NET application with SQL Server 2005 Express Edition into one. So that users can install and uninstall from one place with minimal user intervention. It seems to be such a common task, but it's certainly not too intuitive.
William
|||I too want to have the ability to uninstall a named instance of SQL Server 2005 Express SP2 from the command prompt in silent mode? You were you able to find a solution?sqlFriday, March 23, 2012
Installing .NET Framework on a sql server
We have a DTS package which use .NET Exe as 'Execute Process Task'.
As this is a .NET application, it requires .NET Framework. Can we
install .NET Framework on a Production SQL Server.
What are other options?
Thanks a lot for the help.
PalsIf you want to run a .NET application, you have to install the framework. I
have had no problems having the framework on an SQL server. Be aware that
the ADO.NET components require that you update MDAC to at least 2.7 so that
may affect you.
Christian Smith
"DoNotReply" <palmskumar@.yahoo.com> wrote in message
news:31f15ba6.0402201342.13afff7@.posting.google.com...
> We have a DTS package which use .NET Exe as 'Execute Process Task'.
> As this is a .NET application, it requires .NET Framework. Can we
> install .NET Framework on a Production SQL Server.
> What are other options?
> Thanks a lot for the help.
> Pals
As this is a .NET application, it requires .NET Framework. Can we
install .NET Framework on a Production SQL Server.
What are other options?
Thanks a lot for the help.
PalsIf you want to run a .NET application, you have to install the framework. I
have had no problems having the framework on an SQL server. Be aware that
the ADO.NET components require that you update MDAC to at least 2.7 so that
may affect you.
Christian Smith
"DoNotReply" <palmskumar@.yahoo.com> wrote in message
news:31f15ba6.0402201342.13afff7@.posting.google.com...
> We have a DTS package which use .NET Exe as 'Execute Process Task'.
> As this is a .NET application, it requires .NET Framework. Can we
> install .NET Framework on a Production SQL Server.
> What are other options?
> Thanks a lot for the help.
> Pals
Installing .NET Framework on a sql server
We have a DTS package which use .NET Exe as 'Execute Process Task'.
As this is a .NET application, it requires .NET Framework. Can we
install .NET Framework on a Production SQL Server.
What are other options?
Thanks a lot for the help.
PalsIf you want to run a .NET application, you have to install the framework. I
have had no problems having the framework on an SQL server. Be aware that
the ADO.NET components require that you update MDAC to at least 2.7 so that
may affect you.
Christian Smith
"DoNotReply" <palmskumar@.yahoo.com> wrote in message
news:31f15ba6.0402201342.13afff7@.posting.google.com...
> We have a DTS package which use .NET Exe as 'Execute Process Task'.
> As this is a .NET application, it requires .NET Framework. Can we
> install .NET Framework on a Production SQL Server.
> What are other options?
> Thanks a lot for the help.
> Pals
As this is a .NET application, it requires .NET Framework. Can we
install .NET Framework on a Production SQL Server.
What are other options?
Thanks a lot for the help.
PalsIf you want to run a .NET application, you have to install the framework. I
have had no problems having the framework on an SQL server. Be aware that
the ADO.NET components require that you update MDAC to at least 2.7 so that
may affect you.
Christian Smith
"DoNotReply" <palmskumar@.yahoo.com> wrote in message
news:31f15ba6.0402201342.13afff7@.posting.google.com...
> We have a DTS package which use .NET Exe as 'Execute Process Task'.
> As this is a .NET application, it requires .NET Framework. Can we
> install .NET Framework on a Production SQL Server.
> What are other options?
> Thanks a lot for the help.
> Pals
Friday, March 9, 2012
Installation Problem
In the early phases of installation i get the following error message:
This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
i did some research on the web, and i found the same error in SQL Server 2000 refers to having too many instances. In this situation, its not the case. When I narrowed the specifics down to ' sql server 2005' in my search, i'm inconclusive because all answers point in different directions.
Any suggestions?did it create an installation log file? if so, what does it say?|||Oh.. now i see the problem.
It looks for sqlrun.msi when the file i have is called sqlrun_sql.msi.
well i tried to rename the file and reinstall, but intallation did not like that either.
how do i point installation to the correct file?
This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
i did some research on the web, and i found the same error in SQL Server 2000 refers to having too many instances. In this situation, its not the case. When I narrowed the specifics down to ' sql server 2005' in my search, i'm inconclusive because all answers point in different directions.
Any suggestions?did it create an installation log file? if so, what does it say?|||Oh.. now i see the problem.
It looks for sqlrun.msi when the file i have is called sqlrun_sql.msi.
well i tried to rename the file and reinstall, but intallation did not like that either.
how do i point installation to the correct file?
Installation Package for XML Filter
Hi,
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint/...XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay Bhatia
Hi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:
> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint/...XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>
|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint/...XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay Bhatia
Hi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:
> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint/...XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>
|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay
Installation Package for XML Filter
Hi,
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay BhatiaHi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:
> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay BhatiaHi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:
> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay
Installation Package for XML Filter
Hi,
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint.../XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay BhatiaHi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:
> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint.../XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint.../XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay BhatiaHi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:
> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint.../XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay
installation package could not be opened
We tried installing reporting services and first got the error:
"The install has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 25619.
We then installed with the following switch per kb867872:
setup.exe /i"Setup\Rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
Now we get the error:
"This installation package could not be opened. Verify that the package
exists and that you can access it or contact the application vendor to verify
that this is a valid windows installer package."
We have tried different combinations of fully qualified paths for setup.exe
and rsrun.msi with no success and still we continue to get this message.
Anyone know how to get this blanket-blank reporting services installed?
Thanks for your time.Hi.
I've just spent the morning with this problem, and have found a solution!
The command line:
setup.exe /i"Setup\Rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
needs to be similar to this example:
Y:\Sql Reporting Services\setup.exe /iY:\Sql Reporting
Services\Setup\Rsrun.msi RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
ie, ensure you fully qualify all the paths. AND remove the quotation marks
around the ~\Setup\Rsrun.msi parameter!!
Good luck
"pepe" wrote:
> We tried installing reporting services and first got the error:
> "The install has encountered an unexpected error installing this package.
> This may indicate a problem with this package. The error code is 25619.
> We then installed with the following switch per kb867872:
> setup.exe /i"Setup\Rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
> Now we get the error:
> "This installation package could not be opened. Verify that the package
> exists and that you can access it or contact the application vendor to verify
> that this is a valid windows installer package."
> We have tried different combinations of fully qualified paths for setup.exe
> and rsrun.msi with no success and still we continue to get this message.
> Anyone know how to get this blanket-blank reporting services installed?
> Thanks for your time.
"The install has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 25619.
We then installed with the following switch per kb867872:
setup.exe /i"Setup\Rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
Now we get the error:
"This installation package could not be opened. Verify that the package
exists and that you can access it or contact the application vendor to verify
that this is a valid windows installer package."
We have tried different combinations of fully qualified paths for setup.exe
and rsrun.msi with no success and still we continue to get this message.
Anyone know how to get this blanket-blank reporting services installed?
Thanks for your time.Hi.
I've just spent the morning with this problem, and have found a solution!
The command line:
setup.exe /i"Setup\Rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
needs to be similar to this example:
Y:\Sql Reporting Services\setup.exe /iY:\Sql Reporting
Services\Setup\Rsrun.msi RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
ie, ensure you fully qualify all the paths. AND remove the quotation marks
around the ~\Setup\Rsrun.msi parameter!!
Good luck
"pepe" wrote:
> We tried installing reporting services and first got the error:
> "The install has encountered an unexpected error installing this package.
> This may indicate a problem with this package. The error code is 25619.
> We then installed with the following switch per kb867872:
> setup.exe /i"Setup\Rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=TRUE
> Now we get the error:
> "This installation package could not be opened. Verify that the package
> exists and that you can access it or contact the application vendor to verify
> that this is a valid windows installer package."
> We have tried different combinations of fully qualified paths for setup.exe
> and rsrun.msi with no success and still we continue to get this message.
> Anyone know how to get this blanket-blank reporting services installed?
> Thanks for your time.
Wednesday, March 7, 2012
Installation of hotfix package (build 2153) fails
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.
--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
These "failed to read associated hotfix version" error messages are misleading and do not necessary denote a failed install. I've had lots of successful installs that also contained these messages. Can you search you %WINDIR%\hotfix\hotfixsql\Files\sqlrun_sql.msp log for the text string "value 3" and see if there is a more descriptive message?
Thanks,
Sam Lester (MSFT)
Are you installing the hotfixes in the correct order?
SQL Server 2005
SQL Server 2005 Analysis Services
SQL Server 2005 Integration Services
SQL Server 2005 Notification Services
SQL Server 2005 Reporting Services
SQL Server 2005 Tools
http://support.microsoft.com/kb/919224/
|||I am also getting the same error with Enterprise Edition on a cluster while installing build 2153.
The first remote node is successful and then the local node fails
11/02/2006 16:26:51.032 ================================================================================
11/02/2006 16:26:51.042 Hotfix package launched
11/02/2006 16:26:53.009 Product discovery successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.020 SP Level check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.030 Product language check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.040 Product version check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.227 Product discovery successfully completed during the install process for VSQL06
11/02/2006 16:26:53.237 SP Level check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.258 Product language check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.268 Product version check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.278 Command-line instance name check completed during the install process
11/02/2006 16:26:53.320 Baseline build check completed during the install process
11/02/2006 16:27:49.750 Attempting to install instance: MSSQLSERVER
11/02/2006 16:27:49.781 Enumerating passive cluster nodes
11/02/2006 16:27:49.812 Patching available passive node: FMEZ1TMP201
11/02/2006 16:27:49.823 Attempting to patch running passive node: FMEZ1TMP201
11/02/2006 16:27:49.833 Waiting for first successfully completed passive node
11/02/2006 16:27:49.916 Successfully created remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.666 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.676 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.718 Successfully created new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.453 Successfully saved new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.484 Successfully created scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.505 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.515 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:23.543 Scheduled task for product instance target has completed
11/02/2006 16:30:23.563 Waiting for exit code from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.581 Received exit code 0 from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.591 Result code for scheduled task for product instance target has been received
11/02/2006 16:30:28.611 Removed scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.911 Successfully removed remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.931 Remote process completed for product instance target
11/02/2006 16:30:28.941 Exit code for passive node: FMEZ1TMP201 = 0
11/02/2006 16:30:30.941 First successful passive node has been completed
11/02/2006 16:30:30.961 Attempting to install target: FMEZ1TMP200
11/02/2006 16:30:35.190 Attempting to check for locked files: sqlrun_sql.msp
11/02/2006 16:30:35.240 Attempting to check for locked files: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:30:35.260 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
11/02/2006 16:31:03.862 MSP returned 1602: The user cancels installation.
11/02/2006 16:31:04.101 Successfully checked file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:04.121 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
11/02/2006 16:31:04.141 Failed to read registry key: PendingFileRenameOperations
11/02/2006 16:31:04.151 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
~~~~~~~~
~~~~~~~~
11/02/2006 16:31:08.180 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
11/02/2006 16:31:08.380 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:31:08.400 Failed to read registry key: Debug
11/02/2006 16:33:02.798 MSP returned 1603: A fatal error occurred during installation.
11/02/2006 16:33:03.098 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:33:03.108 Failed to read registry key: Debug
11/02/2006 16:33:03.128 Unable to install MSP file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:33:03.138 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/02/2006 16:33:03.138 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
11/02/2006 16:33:03.218
11/02/2006 16:33:03.228 Product Status Summary:
11/02/2006 16:33:03.248 Product: SQL Server Database Services 2005 (64-bit)
11/02/2006 16:33:03.258 MSSQLSERVER - Failure
11/02/2006 16:33:03.278 Details: Unable to install Windows Installer MSP file
11/02/2006 16:33:03.288 VSQL06 - Not Selected
11/02/2006 16:33:03.308
11/02/2006 16:37:36.262 Hotfix package closed
Any ideas?
|||From the hotfix log it may appear that these two issues are the same, however, 1603 is a generic error code for MSP installation which basically just means the install failed. You have to look specifically in the log generated for the MSP to determine the actual cause of failure.
It turns out though that the log with the error for both reports will be located here:
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
You can determine this from these lines in the hotfix log:
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
As Sam suggests, search for "value 3" to try and locate the specific issue causing the failure in both cases. Once you have located it, please post the details so we can troubleshoot this further. Thanks!!
|||bobbins wrote:
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
Installation of hotfix package (build 2153) fails
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.
--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
These "failed to read associated hotfix version" error messages are misleading and do not necessary denote a failed install. I've had lots of successful installs that also contained these messages. Can you search you %WINDIR%\hotfix\hotfixsql\Files\sqlrun_sql.msp log for the text string "value 3" and see if there is a more descriptive message?
Thanks,
Sam Lester (MSFT)
Are you installing the hotfixes in the correct order?
SQL Server 2005
SQL Server 2005 Analysis Services
SQL Server 2005 Integration Services
SQL Server 2005 Notification Services
SQL Server 2005 Reporting Services
SQL Server 2005 Tools
http://support.microsoft.com/kb/919224/
|||I am also getting the same error with Enterprise Edition on a cluster while installing build 2153.
The first remote node is successful and then the local node fails
11/02/2006 16:26:51.032 ================================================================================
11/02/2006 16:26:51.042 Hotfix package launched
11/02/2006 16:26:53.009 Product discovery successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.020 SP Level check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.030 Product language check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.040 Product version check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.227 Product discovery successfully completed during the install process for VSQL06
11/02/2006 16:26:53.237 SP Level check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.258 Product language check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.268 Product version check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.278 Command-line instance name check completed during the install process
11/02/2006 16:26:53.320 Baseline build check completed during the install process
11/02/2006 16:27:49.750 Attempting to install instance: MSSQLSERVER
11/02/2006 16:27:49.781 Enumerating passive cluster nodes
11/02/2006 16:27:49.812 Patching available passive node: FMEZ1TMP201
11/02/2006 16:27:49.823 Attempting to patch running passive node: FMEZ1TMP201
11/02/2006 16:27:49.833 Waiting for first successfully completed passive node
11/02/2006 16:27:49.916 Successfully created remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.666 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.676 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.718 Successfully created new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.453 Successfully saved new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.484 Successfully created scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.505 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.515 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:23.543 Scheduled task for product instance target has completed
11/02/2006 16:30:23.563 Waiting for exit code from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.581 Received exit code 0 from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.591 Result code for scheduled task for product instance target has been received
11/02/2006 16:30:28.611 Removed scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.911 Successfully removed remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.931 Remote process completed for product instance target
11/02/2006 16:30:28.941 Exit code for passive node: FMEZ1TMP201 = 0
11/02/2006 16:30:30.941 First successful passive node has been completed
11/02/2006 16:30:30.961 Attempting to install target: FMEZ1TMP200
11/02/2006 16:30:35.190 Attempting to check for locked files: sqlrun_sql.msp
11/02/2006 16:30:35.240 Attempting to check for locked files: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:30:35.260 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
11/02/2006 16:31:03.862 MSP returned 1602: The user cancels installation.
11/02/2006 16:31:04.101 Successfully checked file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:04.121 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
11/02/2006 16:31:04.141 Failed to read registry key: PendingFileRenameOperations
11/02/2006 16:31:04.151 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
~~~~~~~~
~~~~~~~~
11/02/2006 16:31:08.180 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
11/02/2006 16:31:08.380 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:31:08.400 Failed to read registry key: Debug
11/02/2006 16:33:02.798 MSP returned 1603: A fatal error occurred during installation.
11/02/2006 16:33:03.098 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:33:03.108 Failed to read registry key: Debug
11/02/2006 16:33:03.128 Unable to install MSP file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:33:03.138 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/02/2006 16:33:03.138 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
11/02/2006 16:33:03.218
11/02/2006 16:33:03.228 Product Status Summary:
11/02/2006 16:33:03.248 Product: SQL Server Database Services 2005 (64-bit)
11/02/2006 16:33:03.258 MSSQLSERVER - Failure
11/02/2006 16:33:03.278 Details: Unable to install Windows Installer MSP file
11/02/2006 16:33:03.288 VSQL06 - Not Selected
11/02/2006 16:33:03.308
11/02/2006 16:37:36.262 Hotfix package closed
Any ideas?
|||From the hotfix log it may appear that these two issues are the same, however, 1603 is a generic error code for MSP installation which basically just means the install failed. You have to look specifically in the log generated for the MSP to determine the actual cause of failure.
It turns out though that the log with the error for both reports will be located here:
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
You can determine this from these lines in the hotfix log:
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
As Sam suggests, search for "value 3" to try and locate the specific issue causing the failure in both cases. Once you have located it, please post the details so we can troubleshoot this further. Thanks!!
|||Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
Installation of hotfix package (build 2153) fails
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.
--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
These "failed to read associated hotfix version" error messages are misleading and do not necessary denote a failed install. I've had lots of successful installs that also contained these messages. Can you search you %WINDIR%\hotfix\hotfixsql\Files\sqlrun_sql.msp log for the text string "value 3" and see if there is a more descriptive message?
Thanks,
Sam Lester (MSFT)
Are you installing the hotfixes in the correct order?
SQL Server 2005
SQL Server 2005 Analysis Services
SQL Server 2005 Integration Services
SQL Server 2005 Notification Services
SQL Server 2005 Reporting Services
SQL Server 2005 Tools
http://support.microsoft.com/kb/919224/
|||I am also getting the same error with Enterprise Edition on a cluster while installing build 2153.
The first remote node is successful and then the local node fails
11/02/2006 16:26:51.032 ================================================================================
11/02/2006 16:26:51.042 Hotfix package launched
11/02/2006 16:26:53.009 Product discovery successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.020 SP Level check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.030 Product language check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.040 Product version check successfully completed during the install process for MSSQLSERVER
11/02/2006 16:26:53.227 Product discovery successfully completed during the install process for VSQL06
11/02/2006 16:26:53.237 SP Level check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.258 Product language check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.268 Product version check successfully completed during the install process for VSQL06
11/02/2006 16:26:53.278 Command-line instance name check completed during the install process
11/02/2006 16:26:53.320 Baseline build check completed during the install process
11/02/2006 16:27:49.750 Attempting to install instance: MSSQLSERVER
11/02/2006 16:27:49.781 Enumerating passive cluster nodes
11/02/2006 16:27:49.812 Patching available passive node: FMEZ1TMP201
11/02/2006 16:27:49.823 Attempting to patch running passive node: FMEZ1TMP201
11/02/2006 16:27:49.833 Waiting for first successfully completed passive node
11/02/2006 16:27:49.916 Successfully created remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.666 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.676 Successfully transferred payload to remote product instance target \\FMEZ1TMP201
11/02/2006 16:27:51.718 Successfully created new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.453 Successfully saved new scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.484 Successfully created scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.505 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:27:52.515 Successfully started scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:23.543 Scheduled task for product instance target has completed
11/02/2006 16:30:23.563 Waiting for exit code from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.581 Received exit code 0 from scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.591 Result code for scheduled task for product instance target has been received
11/02/2006 16:30:28.611 Removed scheduled task for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.911 Successfully removed remote folder for product instance target \\FMEZ1TMP201
11/02/2006 16:30:28.931 Remote process completed for product instance target
11/02/2006 16:30:28.941 Exit code for passive node: FMEZ1TMP201 = 0
11/02/2006 16:30:30.941 First successful passive node has been completed
11/02/2006 16:30:30.961 Attempting to install target: FMEZ1TMP200
11/02/2006 16:30:35.190 Attempting to check for locked files: sqlrun_sql.msp
11/02/2006 16:30:35.240 Attempting to check for locked files: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:30:35.260 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
11/02/2006 16:31:03.862 MSP returned 1602: The user cancels installation.
11/02/2006 16:31:04.101 Successfully checked file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:04.121 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
11/02/2006 16:31:04.141 Failed to read registry key: PendingFileRenameOperations
11/02/2006 16:31:04.151 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
~~~~~~~~
~~~~~~~~
11/02/2006 16:31:08.180 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
11/02/2006 16:31:08.380 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:31:08.400 Failed to read registry key: Debug
11/02/2006 16:33:02.798 MSP returned 1603: A fatal error occurred during installation.
11/02/2006 16:33:03.098 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
11/02/2006 16:33:03.108 Failed to read registry key: Debug
11/02/2006 16:33:03.128 Unable to install MSP file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:33:03.138 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/02/2006 16:33:03.138 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
11/02/2006 16:33:03.218
11/02/2006 16:33:03.228 Product Status Summary:
11/02/2006 16:33:03.248 Product: SQL Server Database Services 2005 (64-bit)
11/02/2006 16:33:03.258 MSSQLSERVER - Failure
11/02/2006 16:33:03.278 Details: Unable to install Windows Installer MSP file
11/02/2006 16:33:03.288 VSQL06 - Not Selected
11/02/2006 16:33:03.308
11/02/2006 16:37:36.262 Hotfix package closed
Any ideas?
|||From the hotfix log it may appear that these two issues are the same, however, 1603 is a generic error code for MSP installation which basically just means the install failed. You have to look specifically in the log generated for the MSP to determine the actual cause of failure.
It turns out though that the log with the error for both reports will be located here:
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
You can determine this from these lines in the hotfix log:
11/02/2006 16:31:08.300 Attempting to install file: sqlrun_sql.msp
11/02/2006 16:31:08.360 Attempting to install file: \\FMEZ1TMP200\c$\4abf7684d30ce4aeb614ce\hotfixsql\Files\sqlrun_sql.msp
11/02/2006 16:31:08.370 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
As Sam suggests, search for "value 3" to try and locate the specific issue causing the failure in both cases. Once you have located it, please post the details so we can troubleshoot this further. Thanks!!
|||
bobbins wrote:
Hello.
I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll.--
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \\SRVLEBIZTALK\d$\dd32a156dacc8dbe70a862647d70\hotfixsql\Files\sqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
Sunday, February 19, 2012
Installation error 25619
When installing Reporting Services, I get an error "The
installer has encountered and unexpected error installing
this package. This may indicate a problem with this
package. The error code is 25619. This happens at the very
end of the installation process.
I am using Windows 2000 with SQL server 2000. The report
server and reportservertemp databases are created. I do
not have VisualStudio.Net installed.
I got the same error with BETA2Michael wrote:
> *When installing Reporting Services, I get an error "The
> installer has encountered and unexpected error installing
> this package. This may indicate a problem with this
> package. The error code is 25619. This happens at the very
> end of the installation process.
> I am using Windows 2000 with SQL server 2000. The report
> server and reportservertemp databases are created. I do
> not have VisualStudio.Net installed.
> I got the same error with BETA2 *
I'm having the same problem with exactly the same setup as you. Please
let me know if you resolve it, and I'll do the same.
callenpef
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message345949.html|||*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Michael wrote:
> *When installing Reporting Services, I get an error "The
> installer has encountered and unexpected error installing
> this package. This may indicate a problem with this
> package. The error code is 25619. This happens at the very
> end of the installation process.
> I am using Windows 2000 with SQL server 2000. The report
> server and reportservertemp databases are created. I do
> not have VisualStudio.Net installed.
> I got the same error with BETA2 *
Yes I get the same thing as well!! I also have Sharepoint on the same
Windows 2003 Server and thought it might be related to that. But sounds
like it isn't - I also think it might be due to my IIS6 not being in
its default installation state. If this is the case, thats just
stupid.
Someone please help!!
Ryan
ryancooke
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message345949.html
installer has encountered and unexpected error installing
this package. This may indicate a problem with this
package. The error code is 25619. This happens at the very
end of the installation process.
I am using Windows 2000 with SQL server 2000. The report
server and reportservertemp databases are created. I do
not have VisualStudio.Net installed.
I got the same error with BETA2Michael wrote:
> *When installing Reporting Services, I get an error "The
> installer has encountered and unexpected error installing
> this package. This may indicate a problem with this
> package. The error code is 25619. This happens at the very
> end of the installation process.
> I am using Windows 2000 with SQL server 2000. The report
> server and reportservertemp databases are created. I do
> not have VisualStudio.Net installed.
> I got the same error with BETA2 *
I'm having the same problem with exactly the same setup as you. Please
let me know if you resolve it, and I'll do the same.
callenpef
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message345949.html|||*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Michael wrote:
> *When installing Reporting Services, I get an error "The
> installer has encountered and unexpected error installing
> this package. This may indicate a problem with this
> package. The error code is 25619. This happens at the very
> end of the installation process.
> I am using Windows 2000 with SQL server 2000. The report
> server and reportservertemp databases are created. I do
> not have VisualStudio.Net installed.
> I got the same error with BETA2 *
Yes I get the same thing as well!! I also have Sharepoint on the same
Windows 2003 Server and thought it might be related to that. But sounds
like it isn't - I also think it might be due to my IIS6 not being in
its default installation state. If this is the case, thats just
stupid.
Someone please help!!
Ryan
ryancooke
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message345949.html
Subscribe to:
Posts (Atom)