Siebel Tools Check In with Source Control Integration (srcctrl.bat) is Executed Two Times when Checking In a Project. Siebel Tools Should run Source Control Batch File One Time When Checking In Projects.

(Doc ID 2161705.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Tools - Version 15.9 [IP2015] and later
Information in this document applies to any platform.


On : 15.3 [IP2015] version, Configuration - Dev Env

After upgrading Siebel to 15.3 from Siebel, we needed to change the srcctrl.bat to work with a different source control application.  The source control application software used to be VSS but the company is now using  Team Foundation Server (TFS) for Source Control.  The srccrtl.bat was updated accordingly but when a Project is checked into the server in Siebel Tools, the srcctrl.bat file is executed twice.  The second time the batch file is executed, the checkin to the source control fails because the project.sif file has no differences from the project.sif file already in the source control application. 

As a recap here is the process flow:

-File gets checked out from Siebel Server and .sif file is created in C:\Siebel\\Tools\temp\Objects. File shows as 'checked out' in TFS

-Select 'check in object' in Siebel Tools and enter comments.
-.sif file is removed from C:\Siebel\\Tools\temp\Objects
-'checkin' & 'checkout' is called as 2 command line windows open
-'checkout' gets invoked first as the .sif file reappears in the Objects directory
-'checkin' is invoked but since the file is the same as in TFS message 'The following changes were not checked in because the items were not modified.
Undoing edit: c:\Siebel\\Tools\temp\Objects\Business_Service-ABO_Bulk_Request_Explode_Service.sif' is received in xml.log.

Why does the srccrtl bat file get run two times when checking in the project to the server? 

The srccrtl.bat log file shows that the batch file is run two times when a project or projects are checked in.

The issue can be reproduced at will with the following steps:
1. Set up a local Siebel Tools Developer database and do a full get from the server repository.
2. It is not necessary to have a source control software application to reproduce the fact that srcctrl.bat is executed two times when doing a single check in of a project to the server.
3. Change the srcctrl.bat file so that the LOG variable points to a valid file name.
4. Check out a project and then check it back into the server.
5. Review the log file and note that the log file has the logging from the srcctrl.bat file being executed two times.

The source control integration does work to check in the .sif files to the source control application, but the second time the srcctrl.bat file is run when a project is checked in, the check in to the source control application fails because there is no changes between the .sif file being checked in and the .sif file in the source control integration application.


This behavior was found after upgrading to Siebel 15.13 from Siebel


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms