Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

IP2017.6 - Adding a second Siebel Server fails when just Siebel Server and EAI components are instal

edited Mar 31, 2018 5:00AM in Siebel System Admin, Install and Upgrade (MOSC) 1 commentAnswered

Hi All

I am in the process of installing adding a second Siebel Server to the enterprise (Siebel IP2017.patchset6 - windows 2012).  During the step to apply the profile in the SMC,  the following error was generated:

"The origin server did not find a current representation for the target resource or is not willing to disclose that one exists."

So I started reviewing the logs and  comparing as well as comparing the file content of the directory "D:\siebel\ses\applicationcontainer\webapps\siebel" on both servers.   What was interesting was the significant difference in the size of the directories (~40MB vs 17MB).

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center