The customer observed the same error mentioned in this thread:
When running a quick report in Campus Manager (User Tracking > Reports) the following error appears:
Application error: URN_NOT_FOUND : urn "ogs_server_urn" : Not found !!.
Also, the reason here was the same, a config file with with wrong content:
Interestingly, the file was touched when a specific job started. So I assume that this job somehow scrambles up that file.
the content of the "wrong" file was:
#Thu Jul 01 11:35:32 CEST 2010
Also I found a strange "copy" of that file (or part of it) here: /opt/CSCOpx/nullctm_config.txt
root@server # cat /opt/CSCOpx/nullctm_config.txt
#Sat Jul 10 11:40:22 CEST 2010
the timestamp of both files:
-rw-rw-r-- 1 casuser casusers 226 Jul 10 11:40 /opt/CSCOpx/MDC/tomcat/webapps/cmapps/WEB-INF/lib/ctm_config.txt
-rw-r----- 1 casuser casusers 70 Jul 10 11:40 /opt/CSCOpx/nullctm_config.txt
The job showed up with /usr/ucb/ps -gauxwww as follows:
If I remember well this job was of the type "Switch Port Report-Switch Port Summary". But I could not see this job. The reason for this could be that there were a huge amount of jobs listed in CS > Server > Admin > Job Browser: more then 30 000 history entries.
After cleaning up the number of history jobs, the same error appeared again a few day later. What can cause this strange error ?
You can add the property to both files. It does not hurt.
Note the line REGISTRY_LOCATION in the cmapps file. This line tells CSTM where to find its registry files. There is only one registry that is shared between both Campus Manager and UT (campus and cmapps). Therefore, you will never see a registry under the cmapps directory tree.
The bug is not being fixed in LMS 4.0. It will be release noted, and a fix is expecting in a future release. The files are opened for read-write access since the port number property may need to be updated if the port in question is already being used. Adding the DYNAMIC_PORT_ALLOCATION=0 property ensures that the files are never overwritten, but could lead to a port conflict if another, non-LMS app tries to occupy the configured CSTM TCP port.