Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CE10 clustered CMS not seeing repository objects

Status
Not open for further replies.

chris777

MIS
Jan 3, 2002
228
US
This is a CE10 install with a SQL Server 2000 system database.

I added a CMS to an existing cluster (this is the 2nd of two CMSs). I can see the reports and instances ok, but when a report runs it sometimes errors that it 'cannot find repository objects'. I assume this error is thrown when the 2nd CMS is kicking off the recurring object. Also, when I log onto the CMS through the Business View manager and View the repository Explorer, it doesn't show me any objects even though the first CMS does.

The CMSs are runing the same domain admin account. CE10 is the only thing running on the machine with the CMS, Cache and WCS servers installed.

For the original install, I selected a "New" install and then manually clustered the CMSs. I then uninstalled the software (including cleaning out the regsitry) and reinstalled as a "Modified". The results are the same.

Any suggestions??

Chris
Data Intelligence Group
 
Hi,
I'd double check that both CMS services are using the same database and that both have full CRUD rights.

Is there anything in common about the type of object it cannot find?




[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Turkbear,

1) Both CMSs are using a machine DNS which use the same SQL Server logon. In SQL Server that account is the DBO and Owner.

2) The CMS cannot see anything in the repository. It can see the objects/instances/users in the System database but cannot see any repository objects: functions/business views/images/etc. I know the Repository and System database are one and the same, that's is what is driving me crazy about this.

Thanks,


Chris
Data Intelligence Group
 
Well, I figured it out. The problem was the B.V. SDK was not installed on the second server. It appears that when you install a new CMS and DO NOT install a data source (whether MSDE or ODBC) you have to ensure the B.V. SDK is set to install. If you choose a custom install it is a sub-item under the CMS.



Chris
Data Intelligence Group
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top