Search This Blog

SBL-CDM-00166: Error copying file.

Applies to:

Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 5.6

This document was previously published as Siebel SR 38-3345221661.


SBL-CDM-00166, SBL-OMS-00203, SBL-OMS-00107

Dear Siebel Support Team , I am working on configuring Siebel Anywhere for our Siebel 7.8 application and I am receiving errors like SBL-OMS-00203 or SBL-OMS-00107;
Upgrade Kit Wizard OMSV did not complete successfully
ObjMgrBusServiceLog    Error    1    0    2007-05-07 14:26:58    (service.cpp (666)) SBL-CDM-00166: Error copying file.
GenericLog    GenericError    1    0    2007-05-07 14:26:58    Object manager error: ([0] Error copying file.(SBL-CDM-00166) (0x904c))
GenericLog    GenericError    1    0    2007-05-07 14:26:58    ( (0) err=4300107 sys=36940) SBL-OMS-00107: Object manager error: ([0] Error copying file.(SBL-CDM-00166) (0x904c))

I have searched on Siebel Support and I am working with all available documentation but I would like to have your expert opinion on this case ? Is this a Siebel 7.8 Bug ?
Regards - Patrick


Message 1

For the benefit of other users:

Problem: see decription


The "UNC Path for SRF file" should be set to Universal Naming Convention (UNC) path and file name of the standard (complete) .srf file to include in a Standard Repository File upgrade kit.

According to the provided log file, UNC Path for SRF file was set to \\mlbsbldevb1vm\RELEASE

"UpgKitBldrLog    UpgKBError    1    0    2007-05-08 08:48:05    Error copying \\mlbsbldevb1vm\RELEASE to E:\sea78\siebsrvr\temp\UpgKitTmp1-SJ5BL\RELEASE. Make sure \\mlbsbldevb1vm\RELEASE exists and accessible, you have write access to E:\sea78\siebsrvr\temp\UpgKitTmp1-SJ5BL and there is enough disk space."

The problem has been resolved by setting this parameter to


reason: siebel.srf was missing.

Thanks and Regards,

Oracle Product Support
Keywords: Anywhere; srf; SBL-CDM-00166;Error copying file

No comments:

Post a Comment