Error 15457

I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?It's not a "real" error, since the severity is 0. It's safe to ignore it.
It's just a PITA.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"john Schuster" <schuster@.llnl.gov> wrote in message
news:2277b01c45d4f$190760d0$a101280a@.phx.gbl...
I recently set up a maintenance plan using the MS SQL
Maintenance plan wizard. Every thing seems to be working
fine with one exception I keep getting the following error:
"Error 15457, Severity 0, Configuration option '%ls'
changed from %ld to %ld. Run the RECONFIGURE statement to
install"
Does anyone know how to solver this?

Error 14258 while creating a publication

Hi all,
I am trying to create a merge-publication (SQL 2000 SP4).
Unfortunately, it is not working because the wizard pops up with error
14258: Cannot perform this operation while SQL Server Agent is
starting. Try again later.
Checked both services, they seem correct. Both are using (the same)
domain-user with sufficient privs to access the SQLServer box. They
both run fine (all in the green) and there are no errors in the logs.
SQL itself runs fine and I can access all data from any computer in the
network.
Just to be sure, I've stopped and restarted both services but the same
error comes back again. I've checked all settings but as far as I can
see, the box is configured properly.
Any ideas?
Thx,
FS
Check out this MS article:
http://support.microsoft.com/?id=303287
John Steen
"Ferry" wrote:

> Hi all,
> I am trying to create a merge-publication (SQL 2000 SP4).
> Unfortunately, it is not working because the wizard pops up with error
> 14258: Cannot perform this operation while SQL Server Agent is
> starting. Try again later.
> Checked both services, they seem correct. Both are using (the same)
> domain-user with sufficient privs to access the SQLServer box. They
> both run fine (all in the green) and there are no errors in the logs.
> SQL itself runs fine and I can access all data from any computer in the
> network.
> Just to be sure, I've stopped and restarted both services but the same
> error comes back again. I've checked all settings but as far as I can
> see, the box is configured properly.
> Any ideas?
> Thx,
> FS
>
>
|||Hmm, I guess I was too fast... Solved the problem already by googling a
bit further. As a thank you for reading I will share the solution :-)
When having MSDTC switched on _and_ using NT-fibres in the SQL
configuration, you can encounter this error. Switching the NT-fibres
off (and stopping and starting the services again) resolved the
problem. MSKB article, aaaaargh, how could I missed it in the first
place...
From Ferry :
> Hi all,
> I am trying to create a merge-publication (SQL 2000 SP4). Unfortunately, it
> is not working because the wizard pops up with error 14258: Cannot perform
> this operation while SQL Server Agent is starting. Try again later.
>

Error 14258

Hi,

I am new to the organization that I am working and we are running SQL Server 200O server. System has been working fine till last couple of days (It running for past two years).

SQLAGENT.exe has been using almost 50% of the CPU time so yesterday I started the SQL server. I want to modify some of the SQL server JOB but when I click on the properties of any job it gives me the following error:

"Error 14258 - Cannot perform this operation while SQL server agent is starting. Try again later."

I checked SQLAGENTSERVICE service and it is started also in the service manager it shows as started. We have a backup job scheduled for 5 days of the weeks but since last 10-12 days it is not running.

Our SQL Server is configured for thread mode processing. I checked for this error in www.support.microsoft.com but the solution given there is something to do with the fiber mode processing.

Could any body tell me why am I getting this error and what is the work around. Everything has been working fine till last two weeks back. Off course SQL server is running as the base product and no service packs have been applied. Other than applying the service pack is there any other solution, since things have been working fine.

Regards

VbabsDid you restart the MSSQLServer service as well ? Have you rebooted the server ? What version of sql are you using including service pack ? What do the logs report back to when this first started (look at both sql server and event logs) ?|||Originally posted by rnealejr
Did you restart the MSSQLServer service as well ? Have you rebooted the server ? What version of sql are you using including service pack ? What do the logs report back to when this first started (look at both sql server and event logs) ?

Hi,

I have rebooted server twice and all the service including SQLAGENTSERVICE show started. MSSSQLSERVER service stopped and restarted and server is working fine. As I have written erlier, NO SERVICE packs have been applied so far, it is running on the base product (ORIGINAL SQL SERVER 2000). This has been working for past two years (from 2001 onwards) and just last two days back this error poped up.

Also after now 72 hours of restart the agent service shows the same status (STARTED) but in the enterprise manager it still gives the same error.

Help!!!

Cheers

Vinod|||What is displayed in the sql server agent log (as well as the sql logs) when this error is returned ? Also, update your ss to the highest service pack that you can.sql

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I ca
n
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have th
e
same problem? Or maybe deleting the existing maintenance plan and creating i
t
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected database
s
> running at regular intervals through SQLAgent. The backups are working; I
can
> restore the databases. But starting a few weeks ago we've been getting err
or
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backup
s
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage
)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Serve
r
> "ERRORLOG" text file also contains no error messages in connection with th
e
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestion
s
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have
the
> same problem? Or maybe deleting the existing maintenance plan and creating
it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried runnin
g
> the package manually from SSIS (like using the Execute Package Utility) an
d
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
>|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:
> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
> > We have a maintainance plan for full/diff/log backups of selected databases
> > running at regular intervals through SQLAgent. The backups are working; I can
> > restore the databases. But starting a few weeks ago we've been getting error
> > messages in the system event log.
> >
> > First, there's an entry confirming the successful completion of the backups
> > with ID 18265 (source MSSQL$...)
> > Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> > followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> > Error ..." (source SQLAgent$...)
> >
> > As I said, the backups themselves seem to be successful, and the SQL Server
> > "ERRORLOG" text file also contains no error messages in connection with the
> > plans.
> >
> > This is still worrying us a bit, because we fear there might be a good
> > reason for these error messages, and obviously we want to be quite certain
> > that our backups are working properly and will be available if and when we
> > need them.
> >
> > Does anyone have any insight/advice on Error 12291?
> >
> > Thanks
> > Tom Juergens|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:
> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom Juergens
Hi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>

error 1069: The service did not start due to logon problems

The local sql server that was working fine earlier does not start now. I have already created tables and accessed them using stored procedures.

I get an error 1069: The service did not start due to logon problems. I have only changed my domain password. I do not remember what authentication I chose for log on.

Any suggestions would be helpful.

Thanks

try this article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q282254

error 1069: The service did not start due to logon problems

The local sql server that was working fine earlier does not start now. I have already created tables and accessed them using stored procedures.

I get an error 1069: The service did not start due to logon problems. I have only changed my domain password. I do not remember what authentication I chose for log on.

Any suggestions would be helpful.

Thanks

try this article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q282254

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :

OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)

I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :

OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)

I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

Error :Execute Trigger From Remote Server To another Server By Linked Server

i did "Linked server" between To Servers , and it's Working.

For Example :

Server 1 =S1.

Server = S2.

i create table in S1 : name = TblS1

i create same table in S2 : name TblS2

and i create trigger(name tr_cpD) From S1 in TblS1 For send data To TblS2 in S2

/****************** trigger Code ***************

CREATE TRIGGER dbo.tr_cpD

ON dbo.TblS1

AFTER INSERT

AS

BEGIN

SET NOCOUNT ON;

insert into [S2].[dbname].[dbo].[TblS2] Select ID,Name from inserted

END

**************************************************

result is :

Msg 7399, Level 16, State 1, Procedure tr_cpD, Line 14

The OLE DB provider "SQLNCLI" for linked server "S2" reported an error. The provider did not give any information about the error.

Msg 7312, Level 16, State 1, Procedure tr_cpD, Line 14

Invalid use of schema or catalog for OLE DB provider "SQLNCLI" for linked server "S2". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.

how i can execute this trigger

Just to clarify: does the insert statement work outside of the trigger from the same S1 server?|||

Yes.

it's Work from Stored Procduers without TRAN (Transaction) .

if i use Transaction From Stored Procduers is not work.

Give me same result above.

|||Is MSDTC enabled on both servers? I think insert from the trigger into a linked server is done inside the distributed transaction.
But I would expect some transaction specific error if it was not so.|||

Microsoft proived some solution, how to overcome this problem. Try it.

http://support.microsoft.com/kb/873160

I tried in the LAN its working fine. But, still in the WAN is not working.

Error :Execute Trigger From Remote Server To another Server By Linked Server

i did "Linked server" between To Servers , and it's Working.

For Example :

Server 1 =S1.

Server = S2.

i create table in S1 : name = TblS1

i create same table in S2 : name TblS2

and i create trigger(name tr_cpD) From S1 in TblS1 For send data To TblS2 in S2

/****************** trigger Code ***************

CREATE TRIGGER dbo.tr_cpD

ON dbo.TblS1

AFTER INSERT

AS

BEGIN

SET NOCOUNT ON;

insert into [S2].[dbname].[dbo].[TblS2] Select ID,Name from inserted

END

**************************************************

result is :

Msg 7399, Level 16, State 1, Procedure tr_cpD, Line 14

The OLE DB provider "SQLNCLI" for linked server "S2" reported an error. The provider did not give any information about the error.

Msg 7312, Level 16, State 1, Procedure tr_cpD, Line 14

Invalid use of schema or catalog for OLE DB provider "SQLNCLI" for linked server "S2". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.

how i can execute this trigger

Just to clarify: does the insert statement work outside of the trigger from the same S1 server?|||

Yes.

it's Work from Stored Procduers without TRAN (Transaction) .

if i use Transaction From Stored Procduers is not work.

Give me same result above.

|||Is MSDTC enabled on both servers? I think insert from the trigger into a linked server is done inside the distributed transaction.
But I would expect some transaction specific error if it was not so.|||

Microsoft proived some solution, how to overcome this problem. Try it.

http://support.microsoft.com/kb/873160

I tried in the LAN its working fine. But, still in the WAN is not working.

Error "Object reference not set to an instance" on SQL 2005 Reporting Services

Reporting Services on my production server stopped working. If I try to open it from Management studio, I get the error below.

Already tried installing patch 07-040, re-registering asp.net, and a few other stuff. Can you guys help me?

TITLE: Connect to Server

Cannot connect to GRUMIUM.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.2047.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<meta name="StackTrace" content />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR3366CC; TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLORFF3300; TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR3366CC; TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; colorFF3300; TEXT-DECORATION:underline}

</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>An internal error occurred on the report server. See the error log for more details. (rsInternalError) <a href="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInternalError&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.2047.00" target="_blank">Get Online Help</a></li><ul>
<li>Object reference not set to an instance of an object.</li>
</ul>
</ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span>
</body>
</html>
--. (Microsoft.SqlServer.Management.UI.RSClient)

BUTTONS:

OK

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1761909&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=694364&SiteID=1

This could be a variety of things, but is most likely due to some configuration that got "touched" recently.

What has been monkeyed with in IIS or with the report server configuration recently? Undo those changes!

|||

There has been no recent change to my environment. I tried a lot of things already to try re resolve the issue.

- Installed patch 07-040

http://support.microsoft.com/kb/911300/en-us

- tried re-registering asp.net

- tried removing the xmlns from the web.config file from both reportserver and reportmanager folders

All without success. Don't know what else I can do.

Error "Logon Fail" with crystal repor 11 and sql native language

Hi, I am using VB6 and sometimes when I try to display a report using cristal report 11 , I get this error "Logon Fail", I am working with SQL 2005 ENTERPRISE EDITION.

I want to know if I need an aditional configuration or something like that.

Thank you.

There should be a more datiled error message with the error number and state which explains why the logon failed.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Error "Connection Could not be made to the report server" when attempting deployment

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

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

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.

Error "Connection Could not be made to the report server" when attempting deployment

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

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

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.

Error "Connection Could not be made to the report server" when attempting deployment

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

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

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.

Error "Connection Could not be made to the report server" when attempting deployme

I'm working through the SQL2005 Reporting Services Tutorial. When I try to deploy, I get the error "Connection could not be made to the report server." It appears that I do not have permissions to get to localhost/reportserver (I get a permissions error when just trying to get there directly from "run"). In another forum I saw several people having the same issue. One contributor said that the problem was solved for him by uninstalling SQL2005 and reinstalling using the local system account rather than a windows domain account. I tried that, but am getting the same error. Anyone know how to fix this?

If the error you get from the RS URL is access denied, you may need to get permissions to the report server.

Here's where you can read more on RS security. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_security_v1_3hia.asp

If the error is coming from ASP.NET, there may be a configuration issue with your RS server.

Hope that helps

Tudor Trufinescu

|||

Like you (David) I am having a similar problem I have read through the various posts and any help would grateful

My error message is :-

A connection could not be made to the report server http://localhost/reportserver$sqlexpress. (Microsoft Report Designer)

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

The server committed a protocol violation. Section=ResponseStatusLine (Microsoft.ReportingServices.Designer)

I am running XP Home with

SQL Server 2005 Express Edition with Advanced Servicesand

Microsoft SQL Server 2005 Express Edition Toolkit

I am trying to work through Deploying the AdventureWorks Sample Reports found within the Sample Directory installed with SQL Express. I’m sure I’ve followed the clear guide lines given. I’m actually trying this because another Microsoft tutorial resulted in the same problem.

My initial thought was that the server wasn’t running I tried this step below also found on the Sample Reports instructions:-

Type the Report Manager URL in the address bar of a Web browser. By default, the URL is http://<webservername>/reports. If you are using SQL Server Express, the default URL is http://localhost/reports$SQLExpress.

This didn’t work, I note the URL is different to one generating the error message.What should I expect if this is my first deployment?

Also is it possible to identify if the server is running using Services from Administrative Tools (Control Panel)?

|||

I must apologise after much digging around I found this tiny caveat in the system requirements required to run SQL Server Express with Advanced Services on XP Home

1Reporting Services, which is installed as part of SQL Server Express with Advanced Services, will not install on operating systems that do not include Internet Information Services (IIS).

See http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/RequirementsSQLEXP2005Advanced.htm

I guess this is my problem. I wrongly assumed that Microsoft had taken a similar approach to this VERY VERY annoying IIS problem for XP Home users as they had done with their Visual Web Developer Express editions.

It seems the report writer software works as long as you don’t deploy, so I can at least get an idea on how to use it.

Thanks again and Ihope David has his problem fixed soon

|||

I Guys, Im looking for a bit of help on this matter myself we have installed Sharepoint 2007 and SQL 2005 on a 64 bit Windows 2003 server and im trying to deploy a reporting service site each time i do i get

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://srv1-tcrb/ReportServer.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Error</title></head><body>%1 is not a valid Win32 application.
</body></html>
--. (Microsoft.ReportingServices.Designer)

Its not the sites themselves i have deployed them on another server all is ok.

I have tried to replicated the setup of the working server on this one but still the same

Bit more info when i try and connect to or run repors or report server from iis or directly i get HTTP500 internal server error.

any help will be appreciated.

|||

I faced the same problem...

I tried many funny things... initially, I got it to work a bit and not entirely.

You can check out my documented troubleshooting events here.

But the conclusion is like what you have mentioned.

Eventually, the real solution is to reinstall SQL Server 2005 Express with Advance Features (reporting services) using default settings (local system account and also for Report Server) and then it worked! But actually I reinstalled two times.

But it could be possible that during previous installations, certain settings were skipped by the installer and caused the misbehaviour.

|||

Thislink may help u ?

http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/rsdepgd.mspx

Side-side by Installation SPS and SSRS

|||At the risk of sounding and appearing stupid try using the url in the format http://servername/reportserver2005. Adding the 2005 at the end did the trick for me.|||

That is a link for Sql Reporting from 2000. I have the problem for 2005.

I have already checked

Deploying Reporting server http://technet.microsoft.com/en-us/library/ms159868.aspx

Troubleshooting Reporting Server http://technet.microsoft.com/en-us/library/ms159135.aspx
But I can not seems to find a solution.

Error "Line too long" - Report too large?

I'm working with a report which is being generated dynamically through
an XML and XSLT transform which generates the .rdl file which is then
pasted in to the code view of a report file in Visual Studio. This
process has worked so far for various reports until we came to this
latest report.
This report is a bit larger in scale, all together the final file size
of the .rdl file is just about 2MB. Of course it's a bit slow to work
with in Visual Studio, but the goal again was to generate the .rdl
dynamically so that editing the file(s) in Visual Studio would not be
necessary.
The report loads fine into Visual Studio and the layout view of the
report looks fine as well, but when we attempt to preview the report,
we get a build error which states:
[rsUnexpectedCompilerError] An unexpected error occurred while
compiling expressions. Native compiler return value: '[BC30494] Line
is too long.'.
I've attempted to locate information on the error message or the error
code itself but can't find any references anywhere. The error is
occurring on compilation of the report - because the same error occurs
when we select 'Build' from the context menu of the report.
So since it's a compilation error and the message seems to indicate
that the error occured while compiling expressions (and expressions use
VB.NET syntax) my assumption is that the source of the report is
somehow being passed in as a parameter to a version of the VB.NET
compiler and then spit back out for further processing.
If you follow that logic, my first thought was that perhaps one of the
expressions was literally too long and perhaps needed to be broken up
into smaller lines. But this was not the case. As the longest 'line' in
the report is 384 characters. Not long enough to cause any problems.
And we have other reports with lines just as long which do compile.
My next thought was that the entire source of the .rdl file was being
passed in to the compiler as a single string for parsing and execution
(e.g. turning the expressions into actual values or something similar).
If this is the case, then perhaps it's the actual size (in characters
or bytes) of the .rdl file that was the problem.
That's currently where I am now. I've narrowed it down to a theoretical
file size limit.
While trimming the report down piece by piece, I've discovered that the
same report works when it is in the area of 1.63 MB in size. However,
as soon as the report reaches 1.79 MB in size, this error returns and
the report fails to build.
I've seen other posts and documentation regarding the theoretical or
imposed limits of IIS and other platforms for uploading reports to
report server, but we are still below the 4MB limit.
I've also seen other posts by users who have asked about reports in the
range of <1MB, but ours is clearly outside that range.
So, does anyone have any information related to this error message, any
limits on .rdl file size, or suggestions for getting this to work?In case anyone is interested about this later on, I haven't found a
solution to the problem yet, but have found a workaround.
I was able to break the report up into smaller, more manageable chunks
(each one around 1MB in size) and create a master report and include
each chunk in a subreport.
So that's how I'm dealing with the problem for now, but I'm still
wondering if the errors I've encountered are really related to the size
of the report or something else.|||will.s.smith@.gmail.com wrote:
> In case anyone is interested about this later on, I haven't found a
> solution to the problem yet, but have found a workaround.
> I was able to break the report up into smaller, more manageable chunks
> (each one around 1MB in size) and create a master report and include
> each chunk in a subreport.
> So that's how I'm dealing with the problem for now, but I'm still
> wondering if the errors I've encountered are really related to the size
> of the report or something else.
Hi,
Iam have a RDL file where the file size is over 4MB
I have been workiing with it and deploying various versions of this
file size for the past couple of weeks ,without any errors and now
unexpectedly when iam to go live tomm Iam getting this error ,
I really don;t have any clue on how to handle this
Any help would really be appreciated
this is the compiler error iam having
[rsUnexpectedCompilerError] An unexpected error occurred while
compiling expressions. Native compiler return value: '[BC30494] Line
is too long.'.
Basically iam having 24 table data regions each pulling data from the
same dataset with different filtering options
only when i add the last 4 table regions iam gettign this error
Keep in mind that i was not getting this error last week with the same
24 data regions

Error - The report server cannot decrypt the symmetric key?

SSRS had been working fine on my comp till the time i insatlled VS 2005. I have started getting following error since VS2005 install

The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content and then restart the service. Check the documentation for more information. (rsReportServerDisabled) Get Online Help
Bad Data.

Why does this error cropped and how can i fix it? I am using SQL Server 2000.

Thanks

It cropped because VS.NET 2005 did aspnet_regiis.exe. Assuming that you have backed up your encryption key (you did right?), you can use the Reporting Services Configuration utility to restore it. If no backup, do:

"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\RsKeyMgmt.exe" -d

Then, go to the Report Manager and reset the connection string in all data sources.

|||if the above command is executed, it seems like it will delete all the reporting data also.
is that correct?|||Incorrect. Only the ecrypted information will be nuked, i.e. connection credentials, connection strings, and any secure information stored in subscriptions – by default this is only username & password in File Share delivery extension.|||So the actual data is never encrypted in the Reporting Services db? Then in case I never made a backup of the encryption keys, and I have to delete it now, I wouldn't be losing any data; just
connection strings etc. Where do I go about changing these connection strings? Again a newbie question for you, what is the File Share delivery extension?

Thanks|||Excluding snapshots, the actual data is not stored in the report catalog. Yes, you will loose only the data source credentials. You can go to the Report Manager to change them. FSE is about delivering subsribed reports (users can subscribe to reports believe it or not) to a network file share.