Have you tried starting it with the correct URL?
Starting with the right URL should fix the issue.
Hi Luz, of course, I tried, but after the incident weblogicManagedServer failed to start. Now the managedserver start, but I got 404 error.
And in the Enterprise manager Deployments there are the another server's applications now. Thats why I wanted to correct the config.xml
1 person found this helpful
Thanks for the update.
1. You can try comparing the config.xml of Admin Server with the one you have. Managed Server should attempt to download it from Admin Server folder every time that it is restarted.
2. File Backups are the suggested option here.
3. You can also try backing up and deleting
Thank you for your advice, I cleared the cache, but nothing happened.
All the config.xml-s are the same corrupt files.
And I dont have backup, next time I will do.
Do you have OBIEE in a different box that Admin Server (Admin Console) run?
Do you see the config.xml-s from f orabi1.corp.com instead of the ones from orabi.corp.com?
yes, they runing in different box.
After correcting the machine name, and some correction in config.xml and biee_domain.xml what was incorrect after the incident too, now the Bi Server starts, but it wants to load the salesamples.rpd instead of my rpd.
I have two error messages:
The start operation can not be performed on the Dummy BI Servers component.
And in EM I see this: ’Error in getting registered instance names’
The Bi_scheduler and the Biserverconmponent does not want to start.
Any Idea would be appriciated
The biee_domain.xml will contain information about the RPD to load etc, so presuming you restored a different version that would be why. Do you have a known-good backup of this file you can compare against?
When you say the components "does not want to start" -- can you provide the log files for these components, and also the opmn.log?