Error 1603 During Installation

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

Error (8626) while inserting record into table with text field and which is the base for i

I have a problem with inserting records into table when an indexed view
is based on it.
Table has text field (without it there is no problem, but I need it).
Here is a sample code:

USE test
GO

CREATE TABLE dbo.aTable (
[id] INT NOT NULL
, [text] TEXT NOT NULL
)
GO

CREATE VIEW dbo.aView
WITH SCHEMABINDING AS
SELECT [id]
, CAST([text] AS VARCHAR(8000)) [text]
FROM dbo.aTable
GO

CREATE TRIGGER dbo.aTrigger ON dbo.aView INSTEAD OF INSERT
AS
BEGIN
INSERT INTO aTable
SELECT [id], [text]
FROM inserted
END
GO

Do the insert into aTable (also through aView).

INSERT INTO dbo.aTable VALUES (1, 'a')
INSERT INTO dbo.aView VALUES (2, 'b')

Still do not have any problem. But when I need index on view

CREATE UNIQUE CLUSTERED INDEX [id] ON dbo.aView ([id])
GO

I get following error while inserting record into aTable:

-- Server: Msg 8626, Level 16, State 1, Procedure aTrigger, Line 4
-- Only text pointers are allowed in work tables, never text, ntext, or
image columns. The query processor produced a query plan that required
a text, ntext, or image column in a work table.

Does anyone know what causes the error?ing42 (Inga.Korczowska@.gmail.com) writes:
> Do the insert into aTable (also through aView).
> INSERT INTO dbo.aTable VALUES (1, 'a')
> INSERT INTO dbo.aView VALUES (2, 'b')
> Still do not have any problem. But when I need index on view
> CREATE UNIQUE CLUSTERED INDEX [id] ON dbo.aView ([id])
> GO
> I get following error while inserting record into aTable:
> -- Server: Msg 8626, Level 16, State 1, Procedure aTrigger, Line 4
> -- Only text pointers are allowed in work tables, never text, ntext, or
> image columns. The query processor produced a query plan that required
> a text, ntext, or image column in a work table.
> Does anyone know what causes the error?

Did you notice the warning when you created the index:

Warning: The optimizer cannot use the index because the select list of
the view contains a non-aggregate expression.

So the index is not of much use. I guess you have hit a restriction
in SQL Server, which does not report as such in a nice way. When I
run your code in SQL 2005, I get:

Msg 1942, Level 16, State 1, Line 1
Cannot create index on view 'tempdb.dbo.aView'. It contains text, ntext,
image or xml columns.

Which is a more resolute message.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

ERREUR to open a data base with SSMSEE

I installed Visual Studio 2005 Standard Edition which contains SQL Server Express.

I downloaded and installed SQL Server Management Studio Express. It run !

I established a connection server BellFixe\SQLEXPRESS (BellFixe is the name of my computer). Ok.

The command " add " of the function " attach " of SSMSE allows to navigate on the disk and to attach diverse data bases but it refuses to open the directory D:\Documents and Settings\Alain (this path is the base of all my directories of data). This directory appears empty. I cannot thus attach the data bases which are under this directory !

I can open a data base only if it is elsewhere localised.

Why this limitation of access and how to resolve this problem? There is certainly a relation with the management of the users of the PC.

I am only user and administrator of my PC under XP. All my directories of data are under D:\Documents and Settings\Alain. The explorer Windows allows to navigate everywhere the disk.

Tanks.

hi,

the position you specfied is not a good one for such a kind of data as it is meant as "private" storage for the current (aka Alain) logged user... you should modify the path to something available to all users, even if SQLExpress always is run under the credential of the account you specified at install time or later, via the Surface Area Configuration or SQL Server Configuration Manager..

regards

|||

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

This is only an MSDN exercise "Coatch ASP.NET". But it is blocking for me.

Regards

|||

hi,

AchLog wrote:

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

is your SQL Server engine service running under Network Service or Local Service account?

please verify via SQL Server Configuration Manager..

regards

|||

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

|||

AchLog wrote:

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

execute the SQL Server Configuration Manager.. in the SQL Server services locate the SQL Server engine you are dealing with.. right click on it and access it's properties.. you can there see (and set) the account running the services... if you modify it you have to restart the service..

AchLog wrote:

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

the "explanation" is correct... this is the "traditional" way to attach a database to a SQL Server instance via SSMS (and SSMSE), but not to "user instances" as the perform differently...

regards

|||

Tank You Andrea,

The parameters are the following ones :

Name : bellfixe\sqlexpress

ERREUR to open a data base with SSMSEE

I installed Visual Studio 2005 Standard Edition which contains SQL Server Express.

I downloaded and installed SQL Server Management Studio Express. It run !

I established a connection server BellFixe\SQLEXPRESS (BellFixe is the name of my computer). Ok.

The command " add " of the function " attach " of SSMSE allows to navigate on the disk and to attach diverse data bases but it refuses to open the directory D:\Documents and Settings\Alain (this path is the base of all my directories of data). This directory appears empty. I cannot thus attach the data bases which are under this directory !

I can open a data base only if it is elsewhere localised.

Why this limitation of access and how to resolve this problem? There is certainly a relation with the management of the users of the PC.

I am only user and administrator of my PC under XP. All my directories of data are under D:\Documents and Settings\Alain. The explorer Windows allows to navigate everywhere the disk.

Tanks.

hi,

the position you specfied is not a good one for such a kind of data as it is meant as "private" storage for the current (aka Alain) logged user... you should modify the path to something available to all users, even if SQLExpress always is run under the credential of the account you specified at install time or later, via the Surface Area Configuration or SQL Server Configuration Manager..

regards

|||

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

This is only an MSDN exercise "Coatch ASP.NET". But it is blocking for me.

Regards

|||

hi,

AchLog wrote:

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

is your SQL Server engine service running under Network Service or Local Service account?

please verify via SQL Server Configuration Manager..

regards

|||

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

|||

AchLog wrote:

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

execute the SQL Server Configuration Manager.. in the SQL Server services locate the SQL Server engine you are dealing with.. right click on it and access it's properties.. you can there see (and set) the account running the services... if you modify it you have to restart the service..

AchLog wrote:

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

the "explanation" is correct... this is the "traditional" way to attach a database to a SQL Server instance via SSMS (and SSMSE), but not to "user instances" as the perform differently...

regards

|||

Tank You Andrea,

The parameters are the following ones :

Name : bellfixe\sqlexpress