Deployment error: Expected C.0.8.43

We are trying to deploy a report server project from an XP Dev box to a Server2003 production environment.

Both computers are running SQL Server 2005 with SP1 installed.

We have tried to deploy by (1) a deploy over the network and (2) a database backup of the ReportServer database and then a restore to the Server 2003 system.

Both methods give us exactly the same error...

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.43'. To continue, update the version of the report server database and verify access rights.

Why are we getting this error?

Regards,

Gary

Reporting Services data is encrypted. Did you backup and restore the symetric key from the old to the new system ? Otherwiese the information from the report database like report definitions can′t be read.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Check out this link. It does not directly apply to your problem, but it may lead you in right direction for a fix. Using the Configuration tool may be helpfull.

http://blogs.msdn.com/lukaszp/archive/2006/05/18/601340.aspx

DependOnService does not work as expected

I have several services that retrieve their initialization
configuration from a database hosted on a SQL server express. All the
services have the SQL server defined in their DependOnService value in
the registry and should therefore not be launched until the SQL server
is ready to accept their connection. What I observe however is that
only a subset of the services is able to connect to the sql server,
and not even always the same subset.
I have tried to Google this problem but without success. Has no one
out there encountered this problem' If so, is there a solution to it?
Any ideas are welcome,
AriI seem to have found a solution: By pausing for 5seconds between
starting up my services they are all successful in connecting to the
database. The problem seems to be that SQL Server express is not able
to service 'simultaneous' logins.
/Ari
developari@.hotmail.com wrote:
> I have several services that retrieve their initialization
> configuration from a database hosted on a SQL server express. All the
> services have the SQL server defined in their DependOnService value in
> the registry and should therefore not be launched until the SQL server
> is ready to accept their connection. What I observe however is that
> only a subset of the services is able to connect to the sql server,
> and not even always the same subset.
> I have tried to Google this problem but without success. Has no one
> out there encountered this problem' If so, is there a solution to it?
> Any ideas are welcome,
> Ari|||<developari@.hotmail.com> wrote in message
news:1173271735.100019.112430@.s48g2000cws.googlegroups.com...
>I seem to have found a solution: By pausing for 5seconds between
> starting up my services they are all successful in connecting to the
> database. The problem seems to be that SQL Server express is not able
> to service 'simultaneous' logins.
>
More likely that SQL Server takes a few seconds to be ready to accept
connections, after the service starts up.
David|||Hi David,
It was my initial thought that the SQL Server had to wait some time
after the service started up before being able to accept connections.
But then I did some tests that dis-proved it: I tried waiting up to 5
minutes after the computer start-up before starting up the services
and then starting them up all in one go. This gave me the same
problems.
My conclusion is that the server is not able to accept such a rapid
succession of login-attempts.
Can you think of a better way of avoiding this problem then starting
up the services in a bat-file where I wait a few seconds between each
start-up?
/Ari
P.s. The SQL Server service is configured to start up automatically.
David Browne wrote:
> <developari@.hotmail.com> wrote in message
> news:1173271735.100019.112430@.s48g2000cws.googlegroups.com...
> >I seem to have found a solution: By pausing for 5seconds between
> > starting up my services they are all successful in connecting to the
> > database. The problem seems to be that SQL Server express is not able
> > to service 'simultaneous' logins.
> >
> More likely that SQL Server takes a few seconds to be ready to accept
> connections, after the service starts up.
> David

DependOnService does not work as expected

I have several services that retrieve their initialization
configuration from a database hosted on a SQL server express. All the
services have the SQL server defined in their DependOnService value in
the registry and should therefore not be launched until the SQL server
is ready to accept their connection. What I observe however is that
only a subset of the services is able to connect to the sql server,
and not even always the same subset.
I have tried to Google this problem but without success. Has no one
out there encountered this problem' If so, is there a solution to it?
Any ideas are welcome,
AriI seem to have found a solution: By pausing for 5seconds between
starting up my services they are all successful in connecting to the
database. The problem seems to be that SQL Server express is not able
to service 'simultaneous' logins.
/Ari
developari@.hotmail.com wrote:
> I have several services that retrieve their initialization
> configuration from a database hosted on a SQL server express. All the
> services have the SQL server defined in their DependOnService value in
> the registry and should therefore not be launched until the SQL server
> is ready to accept their connection. What I observe however is that
> only a subset of the services is able to connect to the sql server,
> and not even always the same subset.
> I have tried to Google this problem but without success. Has no one
> out there encountered this problem' If so, is there a solution to it?
> Any ideas are welcome,
> Ari|||<developari@.hotmail.com> wrote in message
news:1173271735.100019.112430@.s48g2000cws.googlegroups.com...
>I seem to have found a solution: By pausing for 5seconds between
> starting up my services they are all successful in connecting to the
> database. The problem seems to be that SQL Server express is not able
> to service 'simultaneous' logins.
>
More likely that SQL Server takes a few seconds to be ready to accept
connections, after the service starts up.
David|||Hi David,
It was my initial thought that the SQL Server had to wait some time
after the service started up before being able to accept connections.
But then I did some tests that dis-proved it: I tried waiting up to 5
minutes after the computer start-up before starting up the services
and then starting them up all in one go. This gave me the same
problems.
My conclusion is that the server is not able to accept such a rapid
succession of login-attempts.
Can you think of a better way of avoiding this problem then starting
up the services in a bat-file where I wait a few seconds between each
start-up?
/Ari
P.s. The SQL Server service is configured to start up automatically.
David Browne wrote:
> <developari@.hotmail.com> wrote in message
> news:1173271735.100019.112430@.s48g2000cws.googlegroups.com...
> More likely that SQL Server takes a few seconds to be ready to accept
> connections, after the service starts up.
> David