WCS communications error when restoring to new DB

[brendenm]

Hi all,

I am implementing a disaster recovery site and having trouble getting the WCS working.

I have a new server name (different from the original) and restored the old db to it. Unfortunately it has to be a different name.
I've then used a new DNS to point to the restored db with the CMS.
Then started and enabled the servicers.

I can get to the Admin Launchpad but when I click on the link to the CMC I get the following
"Communication failed with all configured Web Component Servers because they are disabled or not currently running"


I have noticed one big thing!!
If I have the allowed to connect to the original server I find it works.
Now I assume its still trying to access the original server but I thought restoring and connecting to the new db would sort things out.
Do I need to restore the db then "select a new data source", "copy from another data source" or "recreate current data source"?

I think thats along the lines of what I need to do.

It's really annoying trying to get this to work as I keep coming across this WCS issue.

Cheers for any help.

 

[PatBITK]

Hi,

OK, The WCS is something I haven't used in ages but in the CCM, don't you have something called the Web Connector where you specify the name of the APS (or CMS depending of the version)?

When you want to use the old SysDB on a server with a new name, you'll have few probs.

1- The CE/BOE services will still point to the old APS/CMS name (change that in the CCM)

2- The Web Connector still points to the old APS/CMS name.

It's all old stuff now for me but that's in that direction. Tell me if it helps and if now, what version are you with?

Business Objects Consultant and Trainer
BOCP - BOE and CR & Official Migration Specialist

BI Toolkit - Offices in UK and Holland

http://www.bitoolkit.com