This content has been marked as final. Show 5 replies
Can you pls clarify following:
a) are you trying to install em 12c agent on a windows box? If yes then did you follow the cygwin setup steps from here http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cygwin_ssh.htm#CBHCDFCH
Let me know on which step you get this error , this wiill help me to identify the steps causing this
b) you also mentioned install failed, can you share the exact error?
c) What is the agent deploymnet method you are using ? Add host wizrd ( agent push ) or manual agent deployment
d) Can you open an SR for this so that you can share logs with us or email me the install logs and error screeshot
a) All the servers are Windows 2008 R2 64 bit. I followed the set of instructions in the Cygwin setup. The setup did not produce an error. The error was in OEM at the time of the agent deployment.
b) no error code just the message: cygwin warning: MS-DOS style path detected
c) adding target manually from OEM
d) I did open an SR and sent them logs. Can't share logs on the forum due to company rules. Can provide a screenshot but it shows the same message as above plus server path information.
Thanks maddox for updating me. Can you share the Sr number with me, i will look at it. This is a know issue and have a mos note 1489302.1 on this that you can refer.
Going by your last update : this warning that you see while doing agent deployment is created by Cygwin and it will be like this:
Error Message:cygwin warning:
MS-DOS style path detected: c:/agent
Preferred POSIX equivalent is: /cygdrive/c/agent
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
the warning suggests, setting the CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Per Cygwin documentation
On the usage of a DOS path (C:\foo, \foo\bar), the Cygwin DLL emits a warning that DOS paths shouldn't be used.
Oracle support stopped responding on the SR so I rebuilt the OEM server completely. Finally got past the error that way.
Can you share the SR number so that we can look at the details?