Error Installing RS with exising DB

I am getting the following error while attempting to install RS on a Small
Business Server 2000 box that already contains the ReportServer DB from a
previous setup where the Web portion of RS resided on another box.
The error is:
"A database with the specified name (ReportServer) already exists and is not
a valid report server database. You must either remote the existing database
or select a new database name."
What may be wrong?
Tx
AndyRS won't allow you to install onto a DB that already exists locally. If the
RS that used this database is not needed anymore, then just delete it (and
the temp database associated with it), then you can install. Or you can just
select a new name for the database when running setup.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy Schmidt" <andys@.minunteclinic.com> wrote in message
news:ub2%23zNz$EHA.1296@.TK2MSFTNGP10.phx.gbl...
>I am getting the following error while attempting to install RS on a Small
> Business Server 2000 box that already contains the ReportServer DB from a
> previous setup where the Web portion of RS resided on another box.
> The error is:
> "A database with the specified name (ReportServer) already exists and is
> not
> a valid report server database. You must either remote the existing
> database
> or select a new database name."
> What may be wrong?
> Tx
> Andy
>|||Daniel,
I don't want to re-create all of the folder structure, permissions, etc. If
I create a new db is there a way to import from the old db's tables?
Tx
Andy
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:#6$JXoAAFHA.204@.TK2MSFTNGP10.phx.gbl...
> RS won't allow you to install onto a DB that already exists locally. If
the
> RS that used this database is not needed anymore, then just delete it (and
> the temp database associated with it), then you can install. Or you can
just
> select a new name for the database when running setup.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Andy Schmidt" <andys@.minunteclinic.com> wrote in message
> news:ub2%23zNz$EHA.1296@.TK2MSFTNGP10.phx.gbl...
> >I am getting the following error while attempting to install RS on a
Small
> > Business Server 2000 box that already contains the ReportServer DB from
a
> > previous setup where the Web portion of RS resided on another box.
> >
> > The error is:
> >
> > "A database with the specified name (ReportServer) already exists and is
> > not
> > a valid report server database. You must either remote the existing
> > database
> > or select a new database name."
> >
> > What may be wrong?
> >
> > Tx
> > Andy
> >
> >
>|||You can use rsconfig to point to the old database after you install to a new
database. Just make sure that both db schemas are the same. That is if the
original DB is SP1 make sure to upgrade the new one to SP1 before using
rsconfig. You will most likely then have issues with reading encrypted
data. If you saved off your symmetric key from the old installation, after
using rsconfig you can import the key using rskeymgmt. If you did not save
the old symmetric key, after running rsconfig, run rskeymgmt -d. This will
delete all encrypted data from RS. That means you will need to enter all
your report/data source credential again.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andy Schmidt" <andys@.minunteclinic.com> wrote in message
news:Ohy1KViAFHA.2316@.TK2MSFTNGP15.phx.gbl...
> Daniel,
> I don't want to re-create all of the folder structure, permissions, etc.
> If
> I create a new db is there a way to import from the old db's tables?
> Tx
> Andy
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:#6$JXoAAFHA.204@.TK2MSFTNGP10.phx.gbl...
>> RS won't allow you to install onto a DB that already exists locally. If
> the
>> RS that used this database is not needed anymore, then just delete it
>> (and
>> the temp database associated with it), then you can install. Or you can
> just
>> select a new name for the database when running setup.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "Andy Schmidt" <andys@.minunteclinic.com> wrote in message
>> news:ub2%23zNz$EHA.1296@.TK2MSFTNGP10.phx.gbl...
>> >I am getting the following error while attempting to install RS on a
> Small
>> > Business Server 2000 box that already contains the ReportServer DB from
> a
>> > previous setup where the Web portion of RS resided on another box.
>> >
>> > The error is:
>> >
>> > "A database with the specified name (ReportServer) already exists and
>> > is
>> > not
>> > a valid report server database. You must either remote the existing
>> > database
>> > or select a new database name."
>> >
>> > What may be wrong?
>> >
>> > Tx
>> > Andy
>> >
>> >
>>
>sql

Error in Event Viewer

I am having trouble backing up my SQL DBs using Retrospect software to a NAS
box. I am thinking this error might have something to do with it. What does
it mean? Thanks for any help!
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status: Failed -
Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could not
obtain information about Windows NT group/user 'PULIZ04\Administrator'.
[SQLSTATE 42000] (Error 8198)).The maintenance plan has been made with a user who probably doesn't exist
anymore.
You might try to edit the maintenance plan and use a user name and password
with full admin rights at
the database. Simply right click the maintenance plan and choose edit
properties. Within the properties it's possible to edit the user.
Regards,
Johan
"scottdog129" <scottdog129@.discussions.microsoft.com> schreef in bericht
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).|||Yes, that is the resason for your backup failure. That happens now and then
and there are different causes and fixes. The best way is to avoid such a
problem by changing your job owner to a SQL login such as sa.
Gary
"scottdog129" <scottdog129@.discussions.microsoft.com> wrote in message
news:6E7E1780-9C65-49F6-AFE1-088266C1920C@.microsoft.com...
> I am having trouble backing up my SQL DBs using Retrospect software to a
NAS
> box. I am thinking this error might have something to do with it. What
does
> it mean? Thanks for any help!
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan1'' (0xAE93FC57F4BBB24EAC6F90AD165B993F) - Status:
Failed -
> Invoked on: 2004-11-19 02:00:01 - Message: The job failed. Unable to
> determine if the owner (PULIZ04\Administrator) of job DB Backup Job for DB
> Maintenance Plan 'DB Maintenance Plan1' has server access (reason: Could
not
> obtain information about Windows NT group/user 'PULIZ04\Administrator'.
> [SQLSTATE 42000] (Error 8198)).