Problems installing Reporting Services

Hi Folks,

I want to download Reporting Services for SQL Server Express Edition but I can't find it.

It seems to be in Analysis Services but when I run SQLEXPR_ADV.EXE I don't find any mention of Reporting Services.

I get to the final options choice which offers me 'Database Services' and 'Client Components' but neither of these mentions Reporting Services.

I have installed BI Studio successfully.

I'd be grateful for any and all suggestions.

Thanks a lot.

Barry

You obtain "Reporting Services", you have to download and install SQL Server Express Advanced Services.

See:

SQL Server 2005 Express Edition (Advanced/SSMS)
http://msdn.microsoft.com/vstudio/express/sql/compare/default.aspx
http://msdn2.microsoft.com/en-us/library/ms365247.aspx
http://tinyurl.com/yelwr9

|||

It doesn't seem you read my question very carefully.

|||

hi Barry,

first verify IIS has been properly installed on the hosting computer ()...

uncheck "Hide advanced configuration options" setting..

in the "Feature selection" dialog task wizard, include "Reporting services"

after the "installation whistles" I got
"Reporting Services
The Reporting Services installation options you specified in Setup determine whether further configuration is required before you can access the report server. If you installed the default configuration, the report server can be used immediately. If you installed just the program files, you must run the Reporting Services Configuration tool to deploy the report server."

and it has been properly installed...

regards

|||

Hi Andrea,

Thanks for your reply.

Unfortunately, you told me what to do but not how to do it so I couldn't follow your advice.

Barry

|||

hi Barry,

Barry333 wrote:

Hi Andrea,

Thanks for your reply.

Unfortunately, you told me what to do but not how to do it so I couldn't follow your advice.

Barry

where did you find problems?

regarding IIS installation, goto control panel->Add or remove programs->Add or remove Windows components... check IIS..

the rest of the "message" indicates that, after running the SQLEXPR_ADV.EXE, you have to uncheck the "hid advanced configuration options" check box and proceed with the installation wizard... the very next wizard step is "Feature selection", where you have to specify to install the Report Server as well...

regards

|||

Hi Andrea,

I appreciate your concern.

Thanks

Barry

|||

hi Barry,

did you solve your isue?

regards

|||

Yes, by referring to the three books I recently bought on SQL Server 2005 Express.

One of the obscure problems was that SSE defaults to preventing remote access, which I needed.

Barry

|||

Hi Andrea,

I have put together a short step-by-step Tutorial for installing Reporting Services to help other people.

Would you like to contribute ?

If so, you can look at my draft :-

http://www.databaseanswers.org/pi_best_practice_display/manual.asp?manual_id=MS-RPTSVCS

You might like to consider how to add this part of your email to me :-

"the rest of the "message" indicates that, after running the SQLEXPR_ADV.EXE, you have to uncheck the "hid advanced configuration options" check box and proceed with the installation wizard... the very next wizard step is "Feature selection", where you have to specify to install the Report Server as well.

Regards

Barry

|||

hi Barry,

Barry333 wrote:

You might like to consider how to add this part of your email to me :-

"the rest of the "message" indicates that, after running the SQLEXPR_ADV.EXE, you have to uncheck the "hid advanced configuration options" check box and proceed with the installation wizard... the very next wizard step is "Feature selection", where you have to specify to install the Report Server as well.

* After running the SQLEXPR_ADV.EXE installer just double-clicking on it and after the pre-requisites installation (when required), please uncheck the "Hide advanced configuration options" check box to enable the full wizard and wizard steps experience.. The very next wizard step is "Feature selection", where you have to specify to install the Report Server as well.

sounds good? but I'm not native english speaker, so you should perhaps reconsider your invitation

regards

Problems executing DML via linked server

Hey folks..
I have a linked server that connects to a DB2 database through the OLE DB
for ODBC Providers driver. I have a DSN created and can, through the linked
server run SELECT statements to my heart's content. When I want to run a
simple DELETE, for example (DELETE HCEDB.APPLQUE2), I get the following
error.
Server: Msg 7345, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' could not delete from table '"HCEDB"."APPLQUE2"'.
User did not have sufficient permission to delete the row.
[OLE/DB provider returned message: Multiple-step OLE DB operation generated
errors. Check each OLE DB status value, if available. No work was done.]
[OLE/DB provider returned message: [IBM][CLI Driver] CLI0150E Driver not
capable. SQLSTATE=S1C00]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IRowsetChange::DeleteRows
returned 0x80040e21: DBROWSTATUS_E_PERMISSIONDENIED].
I have gone to a colleague's machine to use a DB2 Client and authenticated
using the same user specified in both the DSN and Linked Server and was able
to execute the DELETE. Any ideas as to cause and resolution?
Thanks..
Peace,
Gary HampsonIf you are using a DELETE FROM (Table Name), beware.
I was doing the same thing on a DB2 Database with some test data given to me
, and I would get the same error when I tried to delete using the Linked Ser
ver, where if I tried to do it straight in the DB2 Console, I could execute
without any problems.
So I ran an Event Monitor. Happens out, the Microsoft OLE DB Provider for OD
BC Drivers turns it into count(*) many "DELETE FROM TABLE WHERE field = ?".
So if your table has 1000 rows, you'll have 1000 Delete Statements run in se
quence. Very inefficent, but it gets the job done. The reason for my error w
as that there were 3 rows that were identical to each other, and so it had 3
identical "DELETE FROM" statements.
My solution: Deleted the replicated rows. It apparantly was an oversight whe
n creating the test data.
I still have an issue with it producing all those Delete Statements though.
I'm currently looking into other ways of doing it.