I'm encountering an error 1603 durring installation of Reporting Services
Enterprise Edition. I've read the knowledge base article about installing
without creating virtual directories but during that install, I get another
error. This error states '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'm pretty sure that I've specified the path to setup.exe and the .msi file
correctly in the command line. I've tried installing as me, a user with
administrative priveleges, and as Administrator and I receive the same error.
There are no log files written that I can see. Can anyone help me with this?
TIA
ErnieErnie,
I had same problem. I did this:
1. copied the the RS setup files to a folder named "ENT" root to the c
drive. This is the same drive as sql is installed.
2. from the command line in the "ENT" folder typed this EXACTLY:
setup /i "C:\ent\setup\rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=True
It worked. Before, I tried several different cominations of paths and
starting locations that did not work. I don't know why but this did the
trick. Hope it helps.
pepe
"ebferro" wrote:
> I'm encountering an error 1603 durring installation of Reporting Services
> Enterprise Edition. I've read the knowledge base article about installing
> without creating virtual directories but during that install, I get another
> error. This error states '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'm pretty sure that I've specified the path to setup.exe and the .msi file
> correctly in the command line. I've tried installing as me, a user with
> administrative priveleges, and as Administrator and I receive the same error.
> There are no log files written that I can see. Can anyone help me with this?
> TIA
> Ernie|||Pepe:
Thanks for the suggestion but it still crashes with the same error message.
I guess I'm hosed.
Ernie
"pepe" wrote:
> Ernie,
> I had same problem. I did this:
> 1. copied the the RS setup files to a folder named "ENT" root to the c
> drive. This is the same drive as sql is installed.
> 2. from the command line in the "ENT" folder typed this EXACTLY:
> setup /i "C:\ent\setup\rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=True
> It worked. Before, I tried several different cominations of paths and
> starting locations that did not work. I don't know why but this did the
> trick. Hope it helps.
> pepe
>
> "ebferro" wrote:
> > I'm encountering an error 1603 durring installation of Reporting Services
> > Enterprise Edition. I've read the knowledge base article about installing
> > without creating virtual directories but during that install, I get another
> > error. This error states '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'm pretty sure that I've specified the path to setup.exe and the .msi file
> > correctly in the command line. I've tried installing as me, a user with
> > administrative priveleges, and as Administrator and I receive the same error.
> > There are no log files written that I can see. Can anyone help me with this?
> > TIA
> > Ernie|||Don't quit trying. I must have tried 25 times before it worked.
"ebferro" wrote:
> Pepe:
> Thanks for the suggestion but it still crashes with the same error message.
> I guess I'm hosed.
> Ernie
> "pepe" wrote:
> > Ernie,
> >
> > I had same problem. I did this:
> > 1. copied the the RS setup files to a folder named "ENT" root to the c
> > drive. This is the same drive as sql is installed.
> > 2. from the command line in the "ENT" folder typed this EXACTLY:
> >
> > setup /i "C:\ent\setup\rsrun.msi" RSDONOTCREATEVIRTUALDIRECTORIES=True
> >
> > It worked. Before, I tried several different cominations of paths and
> > starting locations that did not work. I don't know why but this did the
> > trick. Hope it helps.
> >
> > pepe
> >
> >
> > "ebferro" wrote:
> >
> > > I'm encountering an error 1603 durring installation of Reporting Services
> > > Enterprise Edition. I've read the knowledge base article about installing
> > > without creating virtual directories but during that install, I get another
> > > error. This error states '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'm pretty sure that I've specified the path to setup.exe and the .msi file
> > > correctly in the command line. I've tried installing as me, a user with
> > > administrative priveleges, and as Administrator and I receive the same error.
> > > There are no log files written that I can see. Can anyone help me with this?
> > > TIA
> > > Erniesql
Showing posts with label article. Show all posts
Showing posts with label article. Show all posts
Thursday, March 22, 2012
Error 1603 During Installation
Monday, March 19, 2012
Error 14046: Could not drop article.
Error 14046: Could not drop article. A subscription exists on it.
I get the above error when I try to drop a publication in SQL2k. I do not
show any subscriptions for this publication anywhere. How can I find the
subscription that is blocking me from dropping this publication?
Nevermind, I got it.
In distribution..MSsubscriptions, I found the "rogue" entry, causing this
error. I deleted it, and was then able to successfully delete the
publication.
"JAdams" wrote:
> Error 14046: Could not drop article. A subscription exists on it.
> I get the above error when I try to drop a publication in SQL2k. I do not
> show any subscriptions for this publication anywhere. How can I find the
> subscription that is blocking me from dropping this publication?
I get the above error when I try to drop a publication in SQL2k. I do not
show any subscriptions for this publication anywhere. How can I find the
subscription that is blocking me from dropping this publication?
Nevermind, I got it.
In distribution..MSsubscriptions, I found the "rogue" entry, causing this
error. I deleted it, and was then able to successfully delete the
publication.
"JAdams" wrote:
> Error 14046: Could not drop article. A subscription exists on it.
> I get the above error when I try to drop a publication in SQL2k. I do not
> show any subscriptions for this publication anywhere. How can I find the
> subscription that is blocking me from dropping this publication?
Subscribe to:
Posts (Atom)