Applies to:Siebel System Software - Version: 22.214.171.124 SIA  and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 126.96.36.199  DEU Cons Sec
Database: Oracle 188.8.131.52
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3
This document was previously published as Siebel SR 38-946524365.
Error: versions of installed components do not match
(wanted version: 184.108.40.206, actual version: 220.127.116.11 SIA)
From the Siebel.log file in the Log directory :
2021 2003-03-04 15:50:44 2003-03-04 15:58:33 +0100 00000001 001 001f 0001 09 siebdev 504 500 C:\sea752\tools\log\siebdev(001).log 18.104.22.168  ENUENU
GenericLog GenericError 1 2003-03-04 15:50:44 Error: versions of installed components do not match (wanted version: 22.214.171.124, actual version: 126.96.36.199 SIA)
After further examining the <tools>\bin\sia directory, the customer found that the srlcver.dll file had not been updated to the .211 Maintenance Release version ( the version of the file was still 188.8.131.52 ).
The customer was advised to run the following MS-DOS command from the hard drive where Siebel 184.108.40.206 is installed, and send in the all_enu.txt and all_base.txt, in order to work out what Siebel versions had been installed.
( For example if Siebel 220.127.116.11 is installed in d:\s752, then run the MS-DOS commands from the D: drive )
findstr /s /i 7 enu.txt > d:\all_enu.txt
findstr /s /i 7 base.txt > d:\all_base.txt
Reviewing the customers all_base.txt file, except for the PATCH_BACK directories, there are 30 occurrences of 18.104.22.168 in the all_base.txt file, for example :
sea752\tools\ACTUATE\AFC\base.txt: 22.214.171.124 SIA  LANG_INDEPENDENT patch applied.
sea752\tools\ACTUATE\BIN\base.txt: 126.96.36.199 SIA  LANG_INDEPENDENT patch applied.
sea752\tools\ACTUATE\CACHE\base.txt: 188.8.131.52 SIA  LANG_INDEPENDENT patch applied.
The customer stated they had not patched Actuate, and during the investigation of this Service Request, the customer de-installed Siebel Tools, re-installed Siebel 7.5.2 Tools and then applied the Siebel 184.108.40.206 Maintenance Release afterwards. Siebel Tools now successfully comes up.
Applies to:Siebel System Software - Version: 220.127.116.11  and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows NT Terminal Server
Product Release: V7 (Enterprise)
Version: 18.104.22.168 
Database: Oracle 22.214.171.124
Application Server OS: Microsoft Windows NT Server 4.0 SP 6a
Database Server OS: IBM AIX 4.3.3
This document was previously published as Siebel SR 38-1015424087.
It start and stop immediately with the following log file info.
2021 2003-05-28 09:08:17 2003-05-28 09:08:17 -0400 00000003 001 001f 0001 09 SiebSrvr 16385 370 389 e:\sea752\siebsrvr\log\Siebel.TNNWAPP06.log 126.96.36.199  ENUENU
GenericLog GenericError 1 2003-05-28 09:08:17 Error: versions of installed components do not match (wanted version: 188.8.131.52, actual version: 184.108.40.206 ENU )
GenericLog GenericError 1 2003-05-28 09:08:17 (lstnsvc.cpp 8(113) err=2100147 sys=0) SMI-00147: (lstnsvc.cpp 8: 113) error code = 2100147, system error = 0, msg1 = Error: versions of installed components do not match (wanted version: 220.127.116.11, actual version: 18.104.22.168 ENU ), msg2 = (null), msg3 = (null), msg4 = (null)
GenericLog GenericError 1 2003-05-28 09:08:17 (siebsvc.cpp 9(317) err=2100147 sys=0) SMI-00147: (siebsvc.cpp 9: 317) error code = 2100147, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)
I installed the Windows_Server_ses patch 214 section on the server.
Which component do not match?
SMI-00147: (lstnsvc.cpp 8: 113) error code = 2100147, system error = 0, msg1 = Error: versions of installed components do not match (wanted version: 22.214.171.124, actual version: 126.96.36.199 ENU)
This error can occur if the 214 patch installation did not update all components of the Siebel installation. Results like this are a symptom of installing the patch when the services were active or not having proper administrator rights during the install.
To check if this is the case, submit your vpd.properties file to Technical Support for review. If we see components listed at versions 214 and an earlier version, you will be asked to back-up your current vpd.properties file and your Siebel Root directory before proceeding with either of the following options:
1) Do you have a back-up of the vpd.properties file either from the base or the 211 install? If so, replace the current vpd.properties file with the back-up.
2) If no back-up exists, edit the current vpd.properties file and replace all references of 214 with 211.
If the subsequent install of patch 214 fails, you will have to uninstall the entire Siebel product, and then install the Siebel base build and the 214 patch.
Applies to:Siebel System Software - Version: 188.8.131.52  and later [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 184.108.40.206 
Database: IBM DB2 8.1 FixPack 3
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-3015316631.
Recently we are having CLOSE_WAIT issue frequently in our test environment. There was a new release we put on the test environment several months ago. Now the AIX file system is at 5200-06. DB2 level is at "DB2 v220.127.116.11", "special_15285", "U800789_15285", and FixPak "9".
When the CLose_wait problem happened, we saw 12-200 or more close_waits on the OM servers, most of them are from resonate vip to web server. Once it happened, user can't log in to the server. If the problem happens on both our OM servers, no user can log in to the servers(got login page, but when log in, it hung for long time and finally gave server busy error). Sometimes we can't even get login page.
Recently, we found there are exiting processes on the system, like following:
siebsupp 22350 23026 0 13:50:32 pts/3 0:00 grep exiting
- 35100 - - - <exiting>
- 39082 - - - <exiting>
- 44410 - - - <exiting>
Right now, those are all for our call center obj mgr. And when the pid showing exiting status, the tasks for those PID in srvrmgr still showing running status. Just now two these Pids just disappeared (not in exiting status any more), and I checked those tasks that were under that pid, they all exited with following error message:
Internal: Siebel home directory could not be determined
This is when the pid exiting:
app224 US_CCOM 56272 39082 Running Interactive 2006-04-25 13:45:15 Handling Logon US_CCOM_CG 7 CRMP4007 Normal
This is when the pid is gone:
app224 US_CCOM 56272 Exited with error Interactive 2006-04-25 13:45:15 2006-04-25 13:54:35 Internal: Siebel home directory could not be determined US_CCOM_CG 7 CRMP4...
The customer encountered the following behavior in their preproduction environment.
The customer was encountering a CLOSE_WAIT issue frequently in their test environment.
The end result was that once this occurred users were unable to log in to the server. If the problem happened on both their OM servers, no user could log in to the servers. They received the login page, but when they logged in, it hung for a long time and finally gave server busy error. Sometimes they were not able to get the login page.
The customer was also seeing processes exit with the error "Internal: Siebel home directory could not be determined".
For the processes which were exiting with the above error the customer was advised that this error had been seen previously and the root cause in the past indicated a problem with the userpref filesystem or with the preferences file itself.
The customer was also advised to double check that rpc.lockd and rpc.statd were enabled on the siebel server and that 511 threads were assigned to the lockd.
On searching supportweb the following posting describes a past experience with this setting too low.
Service Request 38-1409228471 entitled "Objectmanager exits with error GEN-00014: Internal: Siebel home directory could not be determined".
The customer was also advised to try the suggestion to set the environment variable MWLOCK_WITHOUT_TIMER=1 on both servers so that the Siebel Server will release locks on processes as per instructions on the following service request on supportweb.
Service Request 38-2294263997 entitled “SIGABART on production”
In this case it was suggested that the SBL-GEN-00014 error message occurred due to a locking issue typically when accessing user preference files from the File System.
On making the above change the customer no longer encountered the CLOSE_WAITs on their server.
However, the customer still encountered cases where the PIDs for Object manager processes were hanging. When this occurred it hung at Handling Logon status. And after the user put in user name and password in the login page, it was hanging there and would never start to launch the Siebel pop up window. If the user kept the hanging session open, it finally returned to "The page can not be displayed" error.
This occurred for any users connecting to this same PID.
In depth analysis was performed on the customer’s environment including performing truss traces on the PIDs in question which showed the last file accessed being the user preference file which had extensions similar to the following:
CRMAUTO10&Siebel Universal Agent.spf_d98capp221_42440_4899
These seemed to be of zero size in the file system.
Some analysis was completed on the file system user preference area as the customer had some customizations around this area but these were not found to be having an influence.
After further investigation it was found that the customer had applied a QuickFix a few months previously.
The customer found that the patch was not showing correctly in enu.txt, base.txt and fra.txt files in /siebel/siebsrvr/admin directory on both servers. They uninstalled and reinstalled the Quick Fix and remonitored the environment.
After doing so no new hangs occurred and the environment behaved correctly.
Applies to:Siebel Anywhere - Version: 7.0.4  to 18.104.22.168  - Release: V7 to V7
Information in this document applies to any platform.
Release(s):V7 (Enterprise), V7 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:srlcvder.dll, SBL-GEN-00015, versions of installed components do not match
This document was previously published as Siebel Alert 1246.
- Document 473956.1 which has information about how Siebel Anywhere cannot upgrade Siebel clients from versions 7.7.2.x to 22.214.171.124 using Delta Client Executables kit.
- Document 473957.1 which has information about how the Siebel Anywhere Delta Client Executables Upgrade kit fails for Siebel Dedicated Web Clients and Siebel Mobile Web Clients because of incorrect versioning.
- Document 473788.1 which has information about how the Delta Repository File upgrade kit fails for Siebel Dedicated Web Clients and Siebel Mobile Web Clients installed in a path which contains spaces.