Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Could not find matching OpenDeploy client for ().
cesarecastro
Has anyone dealt with this error.
Receiver Servers have the odrcvr file setup correctly. These servers stopped working after a windows hotfix install. IW OD services are up and running but do not take in any content. Reciever is Windows 2003 with OD receiver 6.2. Sending Server is Windows 2003 with OD 6.2
LIB: id=m416 2008-11-11 14:01:38 LIB: Component Version (6.2.0.0.0 Build 68916 Interwoven 20071109)
LIB: id=m416 2008-11-11 14:01:38 Protocol Version(5.0) OK
LIB: id=m416 2008-11-11 14:01:38 Connection Id(id=m416)
LIB: id=m416 2008-11-11 14:01:38 platform: server(MSWIN32), client(MSWIN32)
LIB: id=m416 2008-11-11 14:01:38 Transaction Mode: ON
LIB: id=m416 2008-11-11 14:01:38 Mode(normal)
LIB: id=m416 2008-11-11 14:01:38 Protocol(ts_file_list_based)
LIB: id=m416 2008-11-11 14:01:38 Buffer Size (8000)
LIB: id=m416 2008-11-11 14:01:38 Host()
LIB 00006: 2008-11-11 14:01:41 ERROR: Could not find matching OpenDeploy client for ().
ENG: 2008-11-11 14:01:41 PST GMT-08:00 Thread-23 After SETUP res=-1
The parentesis () should have the server name but it does not. Why would that be?
Find more posts tagged with
Comments
cesarecastro
It seems like this is our solution.
run the following command;
d:\Interwoven\OpenDeployNG\jre\bin\java.exe -cp d:\Interwoven\OpenDeployNG\lib\odng.jar com.interwoven.license.LicInfo -f myfile.txt -p OD
And if your config files are good, then you must check the hosts file. Add an entry to the host file with the parameters returned from the command above. and it should work (cross your fingers)
cesarecastro
that didn't work. back to work.
Adam Stoller
that didn't work. back to work.
You may have to tar / zip up your:
and send them to Support (you could post them here, but they're likely to contain information that you don't want to post publicly)
cesarecastro
So here is what happen!
The servers having this issue are produciton servers which reside in the DMZ. Over the past serveral month, these servers were able to resolve the base server's name with the format baseservername.domain but after a reboot this past weekend the servers could not resolve the base server's name anymore hence the blank () in the log file. The blank () was due to the fact that servers in the DMZ can not access the internal dns. How these manage to work correctly and resolve the base server name over the past few months is beyond me because these servers have been in the dmz for a long time, but we can just call it magic.
To fix the issue, we tested if the receiver servers could resolve the IP address of the base server. After the telnet test came back positive, we updated the odrcvr configs with the IP address of the baseserver. After a restart of the OD services the production server started taking in content again.
Webviewer_result.bmp
pdf_result.bmp
ppt_result.bmp