Re-Installing Reporting Server

Discussion:

(too old to reply)

rewritten

2008-08-20 06:09:00 UTC

I am in the situation where I have to re-install an Operations Manager
Reporting Server, due to the original one being no longer available.

I have followed pretty much all the directions I can find. I have removed
all the Management Packs and also all of the Reporting Run-As Accounts, but
cannot remove the Reporting Profiles as the "Delete" option disabled.

I am trying the re-install using the RTM release of Operations Manager 2007,
while the actual Operations Manager 2007 RMS and Agents have been upgraded to
Service Pack 1.

The error I receive is below. I have obviously changed the actual account
name for this post.

-----------------------------

LoadSRSReportsCA try: 0 of 5 success.
MSI (s) (8C:D0) [15:36:55:080]: Executing op:
ActionStart(Name=_SetSRSSecurityCA,,)
Action 15:36:55: _SetSRSSecurityCA.
MSI (s) (8C:D0) [15:36:55:096]: Executing op:
CustomActionSchedule(Action=_SetSRSSecurityCA,ActionType=25601,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) (8C:84) [15:36:55:096]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI378.tmp, Entrypoint: SetSRSSecurityCA
CAPACK: Extracting custom action to temporary directory:
C:\WINDOWS\Installer\MSI378.tmp-\
CAPACK: Binding to CLR version v2.0.50727
Calling custom action
ReportingCAManaged!Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSSecurityCA
SetSRSSecurityCA: SRS Instance is: MSSQLSERVER
SetSRSSecurityCA: full SRS URL is :
http://HO-SQL1:80/Reportserver/ReportService2005.asmx
SetSRSSecurityCA: MOM Server FQDN is: HO-Intranet.seqwater.com.au
SetSRSSecurityCA: Adding Domain\Account to the Report Security
Administrators Group
SetSRSSecurityCA error: Error 777980100, severity 16, state 1 was raised,
but no message with that error number was found in sys.messages. If error is
larger than 50000, make sure the user-defined message is added using
sp_addmessage..
StackTrace: at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)
at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SecuritySpaceOperations.UpsertUserRoles(ICollection`1
urUpdateResults, ICollection`1 urScopeUpdateResults, ICollection`1
urViewScopeUpdateResults, ICollection`1 urTaskScopeUpdateResults,
ICollection`1 urUserUpdateResults)
at
Microsoft.EnterpriseManagement.ManagementGroup.InsertMonitoringUserRoles(ICollection`1 newUserRoles)
at
Microsoft.Reporting.Setup.ReportingManagedCAs.SetUpReportSecurityAdministrator(String managementServerName, String userAccount1, String userAccount2)
at Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSSecurityCA(Session
session)
Action ended 15:37:02: InstallFinalize. Return value 3.
MSI (s) (8C:D0) [15:37:02:596]: User policy value 'DisableRollback' is 0
MSI (s) (8C:D0) [15:37:02:596]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=957643869,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (8C:D0) [15:37:02:627]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
DialogInfo(Type=1,Argument=System Center Operations Manager 2007 Reporting
Server)
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 15:37:02: Rollback. Rolling back action:
Rollback: _SetSRSSecurityCA

-------------------------

Any assistance would be greatly appreciated

Anders Bengtsson [MVP]

2008-08-23 23:58:14 UTC

Permalink

Hi rewritten,

I think that if your management group is SP1 you should use a installation
source with SP1 too, when installing the reporting component of ops mgr.
--
Anders Bengtsson
Microsoft MVP - Operations Manager
Microsoft Certified Trainer (MCT)
http://www.contoso.se

Post by rewritten
I am in the situation where I have to re-install an Operations
Manager Reporting Server, due to the original one being no longer
available.
I have followed pretty much all the directions I can find. I have
removed all the Management Packs and also all of the Reporting Run-As
Accounts, but cannot remove the Reporting Profiles as the "Delete"
option disabled.
I am trying the re-install using the RTM release of Operations Manager
2007, while the actual Operations Manager 2007 RMS and Agents have
been upgraded to Service Pack 1.
The error I receive is below. I have obviously changed the actual
account name for this post.
-----------------------------
LoadSRSReportsCA try: 0 of 5 success.
ActionStart(Name=_SetSRSSecurityCA,,)
Action 15:36:55: _SetSRSSecurityCA.
CustomActionSchedule(Action=_SetSRSSecurityCA,ActionType=25601,Source=
BinaryData,Target=**********,CustomActionData=**********)
C:\WINDOWS\Installer\MSI378.tmp, Entrypoint: SetSRSSecurityCA
C:\WINDOWS\Installer\MSI378.tmp-\
CAPACK: Binding to CLR version v2.0.50727
Calling custom action
ReportingCAManaged!Microsoft.Reporting.Setup.ReportingManagedCAs.SetSR
SSecurityCA
SetSRSSecurityCA: SRS Instance is: MSSQLSERVER
http://HO-SQL1:80/Reportserver/ReportService2005.asmx
SetSRSSecurityCA: MOM Server FQDN is: HO-Intranet.seqwater.com.au
SetSRSSecurityCA: Adding Domain\Account to the Report Security
Administrators Group
SetSRSSecurityCA error: Error 777980100, severity 16, state 1 was raised,
but no message with that error number was found in sys.messages. If error is
larger than 50000, make sure the user-defined message is added using
sp_addmessage..
StackTrace: at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstraction
Layer.HandleIndigoExceptions(Exception ex)
at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SecuritySpaceOpera
tions.UpsertUserRoles(ICollection`1
urUpdateResults, ICollection`1 urScopeUpdateResults, ICollection`1
urViewScopeUpdateResults, ICollection`1 urTaskScopeUpdateResults,
ICollection`1 urUserUpdateResults)
at
Microsoft.EnterpriseManagement.ManagementGroup.InsertMonitoringUserRol
es(ICollection`1 newUserRoles)
at
Microsoft.Reporting.Setup.ReportingManagedCAs.SetUpReportSecurityAdmin
istrator(String managementServerName, String userAccount1, String
userAccount2)
at
Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSSecurityCA(Session
session)
Action ended 15:37:02: InstallFinalize. Return value 3.
MSI (s) (8C:D0) [15:37:02:596]: User policy value 'DisableRollback' is 0
MSI (s) (8C:D0) [15:37:02:596]: Machine policy value 'DisableRollback' is 0
Header(Signature=1397708873,Version=301,Timestamp=957643869,LangId=103
3,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersio
n=4,ScriptAttributes=1)
DialogInfo(Type=0,Argument=1033)
DialogInfo(Type=1,Argument=System Center Operations Manager 2007 Reporting
Server)
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDesc
ription=Removing backup files,CleanupTemplate=File: [1])
Rollback: _SetSRSSecurityCA
-------------------------
Any assistance would be greatly appreciated

rewritten

2008-08-24 22:30:08 UTC

Permalink

Anders,

Thank you for the response. I did get access to Technet and download the
integrated version of the install but to no avail. So I did it the hard way.
Basically the error is generated by a stored procedure executed during the
install. The check appears to be arbitrary and is even tagged with a comment
in the SQL code along the lines or "Yeah well we will do this check and it
could probably prove something, but if it doesn't then just error out.".

Anyway basically the errror was generated because a user role has been
defined by the prious install - which of course is no longer available - so
we had to make the installer think there was no previous install, so we just
commented out the check in the install script and robert is your fathers
brother.

I can hear all those in the distance saying "wrong thing to do", but no this
allowed the install to progress and we checked every stored procedure
execution to make sure we were not going to cause the installation any grief
going forward. Once the installation was successful we ran a "repair"
installation over the top of it and everything came up Donald, so no problems.

Once again thank you for the reponse, it is nice to know people monitor
these forums.

For those who google this post with the same issue (and I have no doubt
there will be unless Microsoft releases a article on how to recover a lost OM
Reporting Server) we had to comment out the following lines:

StoredProcedure [dbo].[p_UserRoleUpsert]

IF EXISTS (SELECT * FROM dbo.UserRole
AND ProfileId = @ProfileId
AND IsSystem = @IsSystem
AND IsScopeFixed = @IsScopeFixed
AND IsHidden = @IsHidden)
RETURN 0

and I am out...

Post by Anders Bengtsson [MVP]
Hi rewritten,
I think that if your management group is SP1 you should use a installation
source with SP1 too, when installing the reporting component of ops mgr.
--
Anders Bengtsson
Microsoft MVP - Operations Manager
Microsoft Certified Trainer (MCT)
http://www.contoso.se

unknown

2010-02-11 16:03:10 UTC

Permalink

I have the exact problem and is so stuck. Tried all, reinstalling, works fine on the old server.

Please describe on how you and where you fixed this

Best regards
Henric

rewritte wrote:

Anders,Thank you for the response.
24-Aug-08

Anders,

Thank you for the response. I did get access to Technet and download the
integrated version of the install but to no avail. So I did it the hard way.
Basically the error is generated by a stored procedure executed during the
install. The check appears to be arbitrary and is even tagged with a comment
in the SQL code along the lines or "Yeah well we will do this check and it
could probably prove something, but if it doesn't then just error out.".

Anyway basically the errror was generated because a user role has been
defined by the prious install - which of course is no longer available - so
we had to make the installer think there was no previous install, so we just
commented out the check in the install script and robert is your fathers
brother.

I can hear all those in the distance saying "wrong thing to do", but no this
allowed the install to progress and we checked every stored procedure
execution to make sure we were not going to cause the installation any grief
going forward. Once the installation was successful we ran a "repair"
installation over the top of it and everything came up Donald, so no problems.

Once again thank you for the reponse, it is nice to know people monitor
these forums.

For those who google this post with the same issue (and I have no doubt
there will be unless Microsoft releases a article on how to recover a lost OM
Reporting Server) we had to comment out the following lines:

StoredProcedure [dbo].[p_UserRoleUpsert]

IF EXISTS (SELECT * FROM dbo.UserRole
WHERE UserRoleId = @UserRoleId
AND UserRoleName = @UserRoleName
AND ProfileId = @ProfileId
AND IsSystem = @IsSystem
AND IsScopeFixed = @IsScopeFixed
AND IsHidden = @IsHidden)
RETURN 0

and I am out...

"Anders Bengtsson [MVP]" wrote:

Previous Posts In This Thread:

On Wednesday, August 20, 2008 2:09 AM
rewritte wrote:

Re-Installing Reporting Server
I am in the situation where I have to re-install an Operations Manager
Reporting Server, due to the original one being no longer available.

I have followed pretty much all the directions I can find. I have removed
all the Management Packs and also all of the Reporting Run-As Accounts, but
cannot remove the Reporting Profiles as the "Delete" option disabled.

I am trying the re-install using the RTM release of Operations Manager 2007,
while the actual Operations Manager 2007 RMS and Agents have been upgraded to
Service Pack 1.

The error I receive is below. I have obviously changed the actual account
name for this post.

-----------------------------

LoadSRSReportsCA try: 0 of 5 success.
MSI (s) (8C:D0) [15:36:55:080]: Executing op:
ActionStart(Name=_SetSRSSecurityCA,,)
Action 15:36:55: _SetSRSSecurityCA.
MSI (s) (8C:D0) [15:36:55:096]: Executing op:
CustomActionSchedule(Action=_SetSRSSecurityCA,ActionType=25601,Source=BinaryData,Target=**********,CustomActionData=**********)
MSI (s) (8C:84) [15:36:55:096]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI378.tmp, Entrypoint: SetSRSSecurityCA
CAPACK: Extracting custom action to temporary directory:
C:\WINDOWS\Installer\MSI378.tmp-\
CAPACK: Binding to CLR version v2.0.50727
Calling custom action
ReportingCAManaged!Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSSecurityCA
SetSRSSecurityCA: SRS Instance is: MSSQLSERVER
SetSRSSecurityCA: full SRS URL is :
http://HO-SQL1:80/Reportserver/ReportService2005.asmx
SetSRSSecurityCA: MOM Server FQDN is: HO-Intranet.seqwater.com.au
SetSRSSecurityCA: Adding Domain\Account to the Report Security
Administrators Group
SetSRSSecurityCA error: Error 777980100, severity 16, state 1 was raised,
but no message with that error number was found in sys.messages. If error is
larger than 50000, make sure the user-defined message is added using
sp_addmessage..
StackTrace: at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)
at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SecuritySpaceOperations.UpsertUserRoles(ICollection`1
urUpdateResults, ICollection`1 urScopeUpdateResults, ICollection`1
urViewScopeUpdateResults, ICollection`1 urTaskScopeUpdateResults,
ICollection`1 urUserUpdateResults)
at
Microsoft.EnterpriseManagement.ManagementGroup.InsertMonitoringUserRoles(ICollection`1 newUserRoles)
at
Microsoft.Reporting.Setup.ReportingManagedCAs.SetUpReportSecurityAdministrator(String managementServerName, String userAccount1, String userAccount2)
at Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSSecurityCA(Session
session)
Action ended 15:37:02: InstallFinalize. Return value 3.
MSI (s) (8C:D0) [15:37:02:596]: User policy value 'DisableRollback' is 0
MSI (s) (8C:D0) [15:37:02:596]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=957643869,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (8C:D0) [15:37:02:627]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
DialogInfo(Type=1,Argument=System Center Operations Manager 2007 Reporting
Server)
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 15:37:02: Rollback. Rolling back action:
Rollback: _SetSRSSecurityCA

-------------------------

Any assistance would be greatly appreciated

On Saturday, August 23, 2008 10:06 PM
Anders Bengtsson [MVP] wrote:

Hi rewritten,I think that if your management group is SP1 you should use a
Hi rewritten,

I think that if your management group is SP1 you should use a installation
source with SP1 too, when installing the reporting component of ops mgr.
--
Anders Bengtsson
Microsoft MVP - Operations Manager
Microsoft Certified Trainer (MCT)
http://www.contoso.se

On Sunday, August 24, 2008 6:30 PM
rewritte wrote:

Anders,Thank you for the response.
Anders,

Thank you for the response. I did get access to Technet and download the
integrated version of the install but to no avail. So I did it the hard way.
Basically the error is generated by a stored procedure executed during the
install. The check appears to be arbitrary and is even tagged with a comment
in the SQL code along the lines or "Yeah well we will do this check and it
could probably prove something, but if it doesn't then just error out.".

Anyway basically the errror was generated because a user role has been
defined by the prious install - which of course is no longer available - so
we had to make the installer think there was no previous install, so we just
commented out the check in the install script and robert is your fathers
brother.

I can hear all those in the distance saying "wrong thing to do", but no this
allowed the install to progress and we checked every stored procedure
execution to make sure we were not going to cause the installation any grief
going forward. Once the installation was successful we ran a "repair"
installation over the top of it and everything came up Donald, so no problems.

Once again thank you for the reponse, it is nice to know people monitor
these forums.

For those who google this post with the same issue (and I have no doubt
there will be unless Microsoft releases a article on how to recover a lost OM
Reporting Server) we had to comment out the following lines:

StoredProcedure [dbo].[p_UserRoleUpsert]

IF EXISTS (SELECT * FROM dbo.UserRole
WHERE UserRoleId = @UserRoleId
AND UserRoleName = @UserRoleName
AND ProfileId = @ProfileId
AND IsSystem = @IsSystem
AND IsScopeFixed = @IsScopeFixed
AND IsHidden = @IsHidden)
RETURN 0

and I am out...

"Anders Bengtsson [MVP]" wrote:

Submitted via EggHeadCafe - Software Developer Portal of Choice
EggHeadCafe Chat Chaos in Silverlight Released Today
http://www.eggheadcafe.com/tutorials/aspnet/325ea67e-d6c4-4811-b096-54f31bdede5d/eggheadcafe-chat-chaos-in.aspx

unknown

2010-04-16 13:53:55 UTC

Permalink

Comment out this part of the stored procedure mentioned in this thread

[OperationsManager].[dbo].[p_UserRoleUpsert]

/*
-- If none of the properties have changed then it is probably a
-- user role user update, hence do not error
IF EXISTS (SELECT * FROM dbo.UserRole
WHERE UserRoleId = @UserRoleId
AND UserRoleName = @UserRoleName
AND dbo.fn_GetDisplayName(UserRoleId, @pref_string) = @UserRoleDisplayName
AND dbo.fn_GetDescription(UserRoleId, @pref_string) = @UserRoleDescription
AND ProfileId = @ProfileId
AND IsSystem = @IsSystem
AND IsScopeFixed = @IsScopeFixed
AND IsHidden = @IsHidden)
RETURN 0
ELSE
BEGIN
RAISERROR(777980100, 16, 1)
GOTO Error_Exit
END
*/

It worked fine for us when we re-installed the Reporting and DW part of ops mgr.

By the way, MS mentioned not to mellow with the database.

Best of luck

//Daniel

Henric Johansson wrote:

Can you explain how to do this?
11-Feb-10

I have the exact problem and is so stuck. Tried all, reinstalling, works fine on the old server.

Please describe on how you and where you fixed this

Best regards
Henric

Previous Posts In This Thread:

On Wednesday, August 20, 2008 2:09 AM
rewritte wrote:

Re-Installing Reporting Server
I am in the situation where I have to re-install an Operations Manager
Reporting Server, due to the original one being no longer available.

I have followed pretty much all the directions I can find. I have removed
all the Management Packs and also all of the Reporting Run-As Accounts, but
cannot remove the Reporting Profiles as the "Delete" option disabled.

I am trying the re-install using the RTM release of Operations Manager 2007,
while the actual Operations Manager 2007 RMS and Agents have been upgraded to
Service Pack 1.

The error I receive is below. I have obviously changed the actual account
name for this post

----------------------------

LoadSRSReportsCA try: 0 of 5 success
MSI (s) (8C:D0) [15:36:55:080]: Executing op:
ActionStart(Name=_SetSRSSecurityCA,,
Action 15:36:55: _SetSRSSecurityCA.
MSI (s) (8C:D0) [15:36:55:096]: Executing op:
CustomActionSchedule(Action=_SetSRSSecurityCA,ActionType=25601,Source=BinaryData,Target=**********,CustomActionData=**********
MSI (s) (8C:84) [15:36:55:096]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI378.tmp, Entrypoint: SetSRSSecurityC
CAPACK: Extracting custom action to temporary directory:
C:\WINDOWS\Installer\MSI378.tmp-
CAPACK: Binding to CLR version v2.0.5072
Calling custom action
ReportingCAManaged!Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSSecurityC
SetSRSSecurityCA: SRS Instance is: MSSQLSERVE
SetSRSSecurityCA: full SRS URL is :
http://HO-SQL1:80/Reportserver/ReportService2005.asm
SetSRSSecurityCA: MOM Server FQDN is: HO-Intranet.seqwater.com.a
SetSRSSecurityCA: Adding Domain\Account to the Report Security
Administrators Grou
SetSRSSecurityCA error: Error 777980100, severity 16, state 1 was raised,
but no message with that error number was found in sys.messages. If error is
larger than 50000, make sure the user-defined message is added using
sp_addmessage.
StackTrace: at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex
at
Microsoft.EnterpriseManagement.DataAbstractionLayer.SecuritySpaceOperations.UpsertUserRoles(ICollection`1
urUpdateResults, ICollection`1 urScopeUpdateResults, ICollection`1
urViewScopeUpdateResults, ICollection`1 urTaskScopeUpdateResults,
ICollection`1 urUserUpdateResults
at
Microsoft.EnterpriseManagement.ManagementGroup.InsertMonitoringUserRoles(ICollection`1 newUserRoles
at
Microsoft.Reporting.Setup.ReportingManagedCAs.SetUpReportSecurityAdministrator(String managementServerName, String userAccount1, String userAccount2
at Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSSecurityCA(Session
session)
Action ended 15:37:02: InstallFinalize. Return value 3.
MSI (s) (8C:D0) [15:37:02:596]: User policy value 'DisableRollback' is 0
MSI (s) (8C:D0) [15:37:02:596]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=957643869,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (8C:D0) [15:37:02:627]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
DialogInfo(Type=1,Argument=System Center Operations Manager 2007 Reporting
Server)
MSI (s) (8C:D0) [15:37:02:627]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 15:37:02: Rollback. Rolling back action:
Rollback: _SetSRSSecurityCA

-------------------------

Any assistance would be greatly appreciated

On Saturday, August 23, 2008 10:06 PM
Anders Bengtsson [MVP] wrote:

Hi rewritten,I think that if your management group is SP1 you should use a
Hi rewritten,

I think that if your management group is SP1 you should use a installation
source with SP1 too, when installing the reporting component of ops mgr.
--
Anders Bengtsson
Microsoft MVP - Operations Manager
Microsoft Certified Trainer (MCT)
http://www.contoso.se

On Sunday, August 24, 2008 6:30 PM
rewritte wrote:

Anders,Thank you for the response.
Anders,

Thank you for the response. I did get access to Technet and download the
integrated version of the install but to no avail. So I did it the hard way.
Basically the error is generated by a stored procedure executed during the
install. The check appears to be arbitrary and is even tagged with a comment
in the SQL code along the lines or "Yeah well we will do this check and it
could probably prove something, but if it doesn't then just error out.".

Anyway basically the errror was generated because a user role has been
defined by the prious install - which of course is no longer available - so
we had to make the installer think there was no previous install, so we just
commented out the check in the install script and robert is your fathers
brother.

I can hear all those in the distance saying "wrong thing to do", but no this
allowed the install to progress and we checked every stored procedure
execution to make sure we were not going to cause the installation any grief
going forward. Once the installation was successful we ran a "repair"
installation over the top of it and everything came up Donald, so no problems.

Once again thank you for the reponse, it is nice to know people monitor
these forums.

For those who google this post with the same issue (and I have no doubt
there will be unless Microsoft releases a article on how to recover a lost OM
Reporting Server) we had to comment out the following lines:

StoredProcedure [dbo].[p_UserRoleUpsert]

IF EXISTS (SELECT * FROM dbo.UserRole
WHERE UserRoleId = @UserRoleId
AND UserRoleName = @UserRoleName
AND ProfileId = @ProfileId
AND IsSystem = @IsSystem
AND IsScopeFixed = @IsScopeFixed
AND IsHidden = @IsHidden)
RETURN 0

and I am out...

"Anders Bengtsson [MVP]" wrote:

On Thursday, February 11, 2010 11:03 AM
Henric Johansson wrote:

Can you explain how to do this?
I have the exact problem and is so stuck. Tried all, reinstalling, works fine on the old server.

Please describe on how you and where you fixed this

Best regards
Henric

Submitted via EggHeadCafe - Software Developer Portal of Choice
BizTalk: Writing and using a custom referenced functoid.
http://www.eggheadcafe.com/tutorials/aspnet/f843db77-a775-415e-bd08-71c2b1127e40/biztalk-writing-and-usin.aspx

Continue reading on narkive:

Search results for 'Re-Installing Reporting Server' (Questions and Answers)

replies

MySQL 5.6 Configuration File ?

started 2013-06-08 09:09:38 UTC

programming & design

replies

Some help please to solve sql server 2005 problem?

started 2009-03-07 13:05:06 UTC

programming & design

replies

Microsoft SQL Server 2005->?