Step CBS make failed while importing
Hi all,
i am getting following errors when i try to import SC SAPPCUI_GP or any other XSS SC.
SAP-JEE is imported successfully but SCA files of ESS, MSS and PCUI are not imported.
the error is
Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before starting the import
Info:waiting for CBS queue activity
Info:build process already running: waiting for another period of 30000 ms (1)
Info:build process already running: waiting for another period of 30000 ms (2)
Info:build process already running: waiting for another period of 30000 ms (24)
Error:CBS error on retrieving open build requests
caused by:Connection refused: connect (Service call exception; nested exception is:
java.net.ConnectException: Connection refused: connect)
com.sap.tc.cbs.client.error.CommunicationException: Connection refused: connect (Service call exception; nested exception is:
java.net.ConnectException: Connection refused: connect)
at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:530)
at com.sap.cms.tcs.client.CBSCommunicator.getOpenBuildRequests(CBSCommunicator.java:1097)
at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1477)
at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:351)
at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:111)
at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:300)
i am getting this connection refused error everywhere now.
i m not able to make out which connection is this ??
is it connection to DB ??
Please help.
regards
ashutosh
Hi Ashutosh,
You may need to restart the CBS service using the Visual Admin.
Regards
Sidharth
Similar Messages
-
CBS Make failed while importing ESS
Hi Experts,
I am importing ESS package as per JDI cookbook. MSS and dependent packages imported fine but ESS package failed after 6 hrs as :
Info:Starting Step CBS-make at 2009-02-12 03:08:11.0390 -8:00
Info:wait until CBS queue of buildspace JDV_XSSTrack_D is completely processed, before starting the import
Info:buildspace = JDV_XSSTrack_D build request id = 6797
Info:wait until CBS queue of buildspace JDV_XSSTrack_D is completely processed, before asking for build results
Info:waiting for CBS queue activity
Info:maximal waiting time is temporally increased
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:no changes on the CBS request queue (JDV_XSSTrack_D) after a waiting time of 21630000 ms
Fatal:The request queue is not processed by the CBS during the given time intervall => the import failed because not every request including follow-up requests were processed
Fatal:Please look after the operational status of the CBS.
Fatal:communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS.
Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2009-02-12 09:25:54.0687 -8:00
There are no other errors, actually import kept running for another 5 hrs ( from activity in temp/CBS folder). There are no other errors.
Any suggestions ? How is "waiitng time 21630000 ms" controlled?
In CBS buildspace information , there are 0 queued/processing/failed requests. **
thanks,
DJHi Daljit,
What is the Databse u are using.
Regards
Deb -
CBS Make failed while importing - Urgent
Hi...
i m following the JDI CookBook to import ESS MSS SCA files.
I have following issues.
1. I have placed all the SCA files, ESS MSS PCUI JBUILT and sap-jee, JTECH in the CMS inbox. but whn i go for check in .. JBUILT AND JTECH are not displayd in the dropdown.
i have successfully checked in sap-jee, ess, mss, pcui sca files and are listed in transport queue
2. i still went ahead with import without JTECH/BUILT files.. Repository import for sap-jee was successful but not the CBS make.
3. this is the error log when i import ess / mss sca files
the repository import itself fails
Info:Starting Step Repository-import at 2005-10-27 18:45:06.0859 +5:00
Info:Component:sap.com/SAP-JEE
Info:Version :NIGHTLYBUILD.20051017041900
Info:4. PR is of type TCSSoftwareComponent
Info:Component:sap.com/SAP_ESS
Info:Version :MAIN_xss04PAT_C.20050908103103
Info:3. PR is of type TCSSoftwareComponent
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: PropagationException received: Could not perform Import Request: Status = 500 Internal Server Error:communication error: PropagationException received: Could not perform Import Request: Status = 500 Internal Server Error
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: PropagationException received: Could not perform Import Request: Status = 500 Internal Server Error
at com.sap.cms.tcs.client.DTRCommunicator.writeChangelistData(DTRCommunicator.java:228)
at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:260)
at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:500)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:169)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:276)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:212)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:432)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:99)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:392)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1156)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1114)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:1025)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:840
Please help me on this as i m having this problem since long. i tried to import a couple of times.
any hint also will be rewarded..!!
regards
ashutoshI don't know if this will be much help, maybe if you could point me to the JDI Cookbook you're using...
Based on the stack trace that you've included, it seems that your client is trying to connect to the DTR and an error is occuring in the operation that the DTR is trying to perform for you.
It's hard for me to assess the full situation without more details, but hopefully that should narrow it down a little bit for you.
-Steve
If you find a post useful, please help keep the community going by setting a good example and rewarding the poster with points. -
CBS - Make Failed for SAP_ESS.sca file
Hi All,
We are trying to implement ESS package in NWDI. All the steps for installation and configuration are done. while importing the sca files in the development tab all the sca file like Jtechs, JEE, Buildt, PCUI are imported successfully.
But SAP_ESS sca file alone is failing. when i went through the log it says repository-import has been finished successfully. But the second step CBS it is failing. When i went through the log it says....
Info:Starting Step CBS-make at 2007-02-26 17:43:05.0671 +5:00
Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before starting the import
Info:waiting for CBS queue activity
Info:build process already running: waiting for another period of 30000 ms (1)
Info:build process already running: waiting for another period of 30000 ms (2).....
When i went through the CBS log the following is the erroe that i received.
Integrate activities into active workspace(s)...
Integration of activities in compartment "sap.com_SAP_ESS_1" started at 2006-09-30 07:16:40.703 GMT
Integration of 1 activities in compartment "sap.com_SAP_ESS_1" finished at 2006-09-30 07:21:08.875 GMT and took 4 m 28 s 172 ms
An incomplete integration in compartment "sap.com_SAP_ESS_1" of buildspace "EPC_ESSTRACK_D" has resulted because of errors during request processing!
Request 169 has been created to re-initialize the compartment
===== Post-Processing ===== finished at 2006-09-30 07:21:09.140 GMT and took 6 m 47 s 859 ms
Change request state from SUCCEEDED to FAILED
ERROR! The following problem(s) occurred during request processing:
Communication error when performing integrations. Server error [500 Internal Server Error]. Request FAILED.
REQUEST PROCESSING finished at 2006-09-30 07:21:19.000 GMT and took 25 m 9 s 500 ms
I tried restarting the server also checked the CBS properties in Visual Admin. It looks everything is fine.
Please help me in this regard.
Thanks,
Nagarajan.Dear Portal gurus,
I too having the same problem . please provide me the solution for this.
how to check the default trace.
regards
prasad -
CBS make fails of SAP_ESS SCA file fails in NWDI 7.0 SP14 after ~4 hours
Hi,
We wish to do ESS customization in our new NWDI 7.0 SP14 system (on RHEL 4.7). Importing the SAPESS09P_3-20000512.SCA (after importing its dependicies) in a ESS track completed in the Repository-import phase but fails in the next CBS-make phase with a timeout of 14430 seconds (~4 hours). The exact error i am getting is listed below. Is their some way to bump up this timeout value?
I am new to this and am very interested in what more experienced folks suggest about this.
thanks in advance,
Steven McElwee, Duke University
20080224153849 Info :Starting Step CBS-make at 2008-02-24 15:38:49.0310 -5:00
20080224153850 Info :wait until CBS queue of buildspace NDI_XSSTrack_D is completely processed, before starting the import
20080224153850 Info :waiting for CBS queue activity
20080224153921 Info :build process already running: waiting for another period of 30000 ms
20080224153951 Info :build process already running: waiting for another period of 30000 ms
20080224154021 Info :build process already running: waiting for another period of 30000 ms
.......... lots more messages
20080224193917 Info :build process already running: waiting for another period of 30000 ms
20080224193947 Info :build process already running: waiting for another period of 30000 ms
20080224194017 Info :no changes on the CBS request queue (NDI_XSSTrack_D) after a waiting time of 14430000 ms
20080224194017 Fatal :The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
20080224194017 Fatal :Please look after the operational status of the CBS.
20080224194018 Info :Step CBS-make ended with result 'fatal error' ,stopping execution at 2008-02-24 19:40:18.0480 -5:00Well, I restored our NWDI system from an archive backup taken just prior to defining the new XSS Track. I then carefully followed the ESS NWDI Cookbook instructions to create the XSS Track and to import everything (SAP-JEE, SAP-BUILDT, SAP-JTECHS, and SAP-PCUI) except for SAP_ESS. I then archived to tape everything again. That was yesterday.
Today, I kicked off the import of SAP_ESS. So far, so good- it imported into the repository and is now in the process of Activation in the CBS. There have been no problems with threads stuck in the CBS queue in the QUEUED state.
Of course, it has been only 2 hours so far.
About the CBS properties for BUILD_TOOL_JDK_HOME,
JDK_HOME_PATHS and idleStart. Aside from idleStart, i have left them unchanged. But will keep this in mind should the previously mentioned wierd CBS behavior return.
Disk space is a little tight right now. I had 4 GB free before the import of SAP_ESS. Now i have 2 GB free, which seems to be holding. We have a script running to archive and delete the oracle redo logs since they are being generated at a pretty fast rate.
Once i know one way or the other about the success of this, i will post a message.
thank you everyone for your help so far!
Steven -
Hi all..
I am trying to import ESS and MSS SCAs.
repository import is finished but CBS make fails.
this is log for CBS make.
Info:Starting Step CBS-make at 2005-11-14 17:43:05.0671 +5:00
Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before starting the import
Info:waiting for CBS queue activity
Info:build process already running: waiting for another period of 30000 ms (1)
Info:build process already running: waiting for another period of 30000 ms (2)
In CBS service, if i select a track and click on info... i get this:
Compile State the current build state of the DC
The DC was built successfully
The Build state of the DC is broken due to a compile error
I have tried restrarting CBS from j2ee engine.. restarted j2ee engine also..but its not working.
i deleted one existing track, restored the system status. again created a track and i got the same error.
please help
regards
ashutoshHi,
For any requestes to be processed by CBS as Andy says above the "Request Processing" should be on and usually the error build process already running comes when the Input mode in CBS is "Previleged". If currenlty any imports are running then the state will be previleged and once the import finishes the mode turns back to open...if it does not turn automatically you might have to manually set it open.
Try to work out with the setting sof buildspace as explained in the links below.
That should help.
These links might be helpful:
BuildSpace views:<a href="http://help.sap.com/saphelp_nw70/helpdata/en/40/372c7fd5ea984c894cb2bfe7472058/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/40/372c7fd5ea984c894cb2bfe7472058/frameset.htm</a>
Managing buildspace
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/35/1cd66947184aa8915ca1831c59b6c1/frameset.htm">http://help.sap.com/saphelp_nw04s/helpdata/en/35/1cd66947184aa8915ca1831c59b6c1/frameset.htm</a>
Component Build Service - Problem analysis scenarios
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/42/c98ced11886babe10000000a1553f6/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/42/c98ced11886babe10000000a1553f6/frameset.htm</a>
Akshatha -
Getting error -- SoapFaultCode:1 Authentication failed while import TP
Hi All,
While importing Transport in PI we are getting the below error;
Deployment
Transport request : XIDK900283
System : XIQ
tp path : tp
Version and release: 375.33.68 710
CTS Deploy Service - Version 0.92 06.03.2007
========================================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/prodtrans/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://test:52200
SoapFaultCode:1 Authentication failed. For details see log entry 002481E407080046000000740000444240
>>>CDB9A36054B360 in security log.
Deployment
End date and time : 20110727180708
Ended with return code: ===> 12 <===
Below is the log when when test in STMS , SAP System ->Check->Transport Tool.
Check Transport Tool 28.07.2011 00:52:09
XIQ System XIQ (PI 7.1 QA)
tp Interface
Transport Profile
RFC Destination
tp Call
Deploy Web Service
Web Service CTSDEPLOY is active
Destination Host=test:52200
Proxy CO_TFLDEPLOY_PROXY_VI_DOCUMENT
Connection Test Exception: cx_ai_system_fault
Deploy Tool
XI URL http://test:52200
XI Logon Data User=NWDI_CTSADM, Password is defined
XI Ping SoapFaultCode:1 Authentication failed..
Please help.
Regards,
Karthik.
Edited by: Karthiksap on Jul 28, 2011 9:14 AMHi Karthik,
Check this link with the same issue:CTS+ For Portal Error: SoapFaultCode:1 Authentication failed
Regards,
Naveen -
Make failed while deploying loan flow
Hi,
when I try to deploy my loan flow sample through Jdeveloper to oracle bpel process manager 10.1.3.1.0
I am getting the following
"Beginning Deployment Process...
Compiling...
[6:54:51 PM] Compilation complete: 0 errors, 1 warnings.
Deploying to http://localhost:9700 domain: default. Please wait....[6:54:51 PM] Deployment failed.
Make failed, so nothing to deploy."
I will glad if some one could help me out.
Thanks
-SagarThanks for the reply.. I restarted and tried next day without making any changes. It deployed succesfully. Probably a rare bug.
I am not using SOA suite. I am using oracle bpel process manager 10.1.3.1.0 alone. Here I think the default is 9700. I checked out http.port= 9700.
And one more thing is bpel server integration status is shown to be ok with 9700 but ESB status is failed. Am I right in assuming that there is no ESB service in oracle bpel process manager 10.1.3.1.0 alone?. I think it is present only in the SOA suite. -
Connection Failed While Importing Metadata
Hi All,
I have installed 11.1.1.6.2 Client on my machine and while i am trying to import metadata it throws an error saying "Connection Failed". Can some one help me how to resolve this ?
Regards,
Vishal BVRI did google it but all the responses were related to the Server versions but not client, none of them answered my question. And coming to your suggestion do you mean that we need to provide full TNS entry i.e.
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl.us.deloitte.com)
or do you want me to mention just ORCL in the DSN name during the import metadata step from the RPD. -
The connection has failed while importing metadata in RPD
Hi All,
Recently I start creating a repository (OBIEE 11g client version 11.1.1.3.0) in offline mode and I want to import metadata which failed by the error ‘The connection has failed’..
Kind Regards,
MohanHi Mohan,
Solution:
1.Copy the tnsnames.ora from Oracle Database home (ORACLE_HOME\NETWORK\ADMIN\) to the following locations.
* \OracleBI1\network\admin (Example: C:\OBI\Oracle_BI1\network\admin)
* \oracle_common\network\admin (Example: C:\OBI\oracle_common\network\admin)
2.Set the TNS_ADMIN environment variable value with one of the copied locations in the step 1 in user.cmd or http://user.sh file depending on your OS.
This file will be found under
\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup
(Example : C:\OBI\instances\instance2\bifoundation\OracleBIApplication\coreapplication\setup)
Thanks,
-Amith. -
"Photoshop Library operation failed" while importing some .psd in AE CS4
Hi
I am currently corking on animating a storyboard and received 58 .psd files from a drawing artist. All files are 886x472 with 5 layers of B&W drawings, representing just 360Mo.
I import them as "composition" since I need to interact with the photoshop layers. the problem is that AE imports the first 28th then stop and a window pops up with that message on it:
Photoshop Library operation failed (most likely out of memory)
First time it happens to me. Does anyone know about this?
Here are my specs:
After Effects CS4 on a PC with, I think, the latest updates
XP Pro 32bit SP3
Intel Core2 Quad CPU - Q9450 @2.66Ghz
with 4Go RAM (well 3,25Go + I did the modification for 3Go in AE)
I have a cache folder on C: with 2000Mo allocated
Here is what I already did:
- clean memory in AE (sorry for the translation, it is "purge" in French), but it did again
- closed PS and Bridge, but it did again
- open a new projetc and tried again, but it did it again
- reboot the system... but it did it againwell some of the psd's have only 4 or 5 layers but it is true that some
have groups withing groups (not a ridiculous amount though).
I did start to unnest them file by file and found one that was corrupted or something
"a problem occured while accessing layers' data. Do you wish to read composite data instead?"
and when I click "yes", it says that it cannot occur since the doc is incompatible w/ my PS version (CS3).
Anyway, I'll let the artist rework that one file and it should be fine.
Thanks for your answer, I really appreciate your valuable input. -
Error - ADD (FAILED : operation failed) while importing a FM in model
Hello,
When I try to import a FM in Web Dynpro Model, it gives me the following Error. What is the error related with. PLease read the error text below? How to resolve this ?
14:19:06.544 ADD (FAILED: operation failed) Raldb_Vari.dtsimpletype.xlf (C:\Documents and Settings\283818\.dtc\0\DCs\pg.com\ezp3\scezp3\dc_model\_comp\src\packages\com\pg\dc_model\models\ezp3model\types\Raldb_Vari.dtsimpletype.xlf)
Regards
MrinaliniHI
are you able to import some other function module successfully or is this the problem with all of them
Thanks
Sarbjeet -
Make fails while building cldc 1.1 on Linux
Dear All,
Following is the software config:
javac : "1.4.2_08"
linux version: redhat linux 9
kernel: 2.4.20-8 on an i686
I am building cldc 1.1 on linux. I am facing a strange problem. After doing a make, the build process stops after these lines
====>
../tools/preverifier/build/linux/preverify -d classes tmpclasses
make[1]: *** [compilefiles] Error 1
make[1]: Leaving directory `/users/in1222c/cldc1/api'
make: *** [all] Error 1
<====
All java files (including custom files that I have included), get compiled to the corresponding class files, but just after the preverification message appears, the build gives an error as above.
Anyone faced this problem yet? If yes, what is that happenning wrong here.
I will be glad for your comment and support on this.
Regards,
Hrishi.Dear All,
Following is the software config:
javac : "1.4.2_08"
linux version: redhat linux 9
kernel: 2.4.20-8 on an i686
I am building cldc 1.1 on linux. I am facing a strange problem. After doing a make, the build process stops after these lines
====>
../tools/preverifier/build/linux/preverify -d classes tmpclasses
make[1]: *** [compilefiles] Error 1
make[1]: Leaving directory `/users/in1222c/cldc1/api'
make: *** [all] Error 1
<====
All java files (including custom files that I have included), get compiled to the corresponding class files, but just after the preverification message appears, the build gives an error as above.
Anyone faced this problem yet? If yes, what is that happenning wrong here.
I will be glad for your comment and support on this.
Regards,
Hrishi. -
Hi,
I tried to import PCUI_GP(.sca file) for development in CMS.
Therefore, I got import failed and error message in CBS-make.
Immediately, I tried to open CBS. But CBS is not opened.
First, I imported following .sca file .
CAF EU
DI BUILD TOOL
EP BUILD TOOL
PORTAL
PORTAL CORE SERVICES
PORTAL FRAMEWORK
PORTAL WEB DYNPRO
SAP J2EE ENGINE
SAP JAVA TECH SERVICES
They were succeeded.
I post error logs in CBS-make.
Info:Starting Step CBS-make at 2006-10-22 10:47:25.0983 +2:00
Info:wait until CBS queue of buildspace VIS_XSS-TEST_D is completely processed, before starting the import
Info:buildspace = VIS_XSS-TEST_D build request id = 107
Info:wait until CBS queue of buildspace VIS_XSS-TEST_D is completely processed, before asking for build results
Info:waiting for CBS queue activity
Error:CBS throws exception during queue waiting:
caused by:Read timed out (Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out)
com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out)
at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:530)
at com.sap.cms.tcs.client.CBSCommunicator.areThereProcessedActivations(CBSCommunicator.java:1603)
at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1643)
at com.sap.cms.tcs.client.CBSCommunicator.getBuildResult(CBSCommunicator.java:914)
at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:142)
at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1540)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by:
java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1800)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:490)
at $Proxy173.getOpenRequests(Unknown Source)
at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:527)
at com.sap.cms.tcs.client.CBSCommunicator.areThereProcessedActivations(CBSCommunicator.java:1603)
at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1643)
at com.sap.cms.tcs.client.CBSCommunicator.getBuildResult(CBSCommunicator.java:914)
at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:142)
at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1540)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1456)
at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1793)
... 53 more
Error:more details on this error:
caused by:Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1800)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:490)
at $Proxy173.getOpenRequests(Unknown Source)
at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:527)
at com.sap.cms.tcs.client.CBSCommunicator.areThereProcessedActivations(CBSCommunicator.java:1603)
at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1643)
at com.sap.cms.tcs.client.CBSCommunicator.getBuildResult(CBSCommunicator.java:914)
at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:142)
at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1540)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1456)
at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1793)
... 53 more
Fatal:communication error: CBS exception received: Read timed out (Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out)
Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-10-22 11:48:05.0061 +2:00
I'm using 2004s SP9.
Any help will be highly appreciated.
Regards,
Yasu.Hi Adrian,
you could do that if you have memory issues in the build, i.e. if the build log (not the request log!) contains e.g. OutOfMemoryExceptions.
Going beyond 1000M on a 32Bit machine is usually not a good idea, I'm not sure if the Sun JDK really supports this. I also know of one case where increasing the size to ~800M helped on a Windows server. Seems like there is some interesting interaction between heap size and garbage collection.
The delay values determine the time it takes for CBS to actually pick up requests for processing, they have no effect on the actual processing time.
For fine tuning I'd put the rootFolder on some fast harddisk. The folder is only used for temporary files and is cleaned up after build. A 5GB partition on a RAID0 with no virus checking would be nice.
Also the threadPoolSize may be interesting as it determines the maximum number of parallel builds. Since not all builds can be executed in parallel and since each build will have its own VM that can be quite resource intensive though and the optimal setting depends on your hardware and the structure of the software you are trying to build.
Regards,
Marc -
Error while importing .SCA files in track
Hi Folks,
I tried importing following .SCA files into a nwdi track but it Finished with Errors.
ENGFACADE
ENGINEAPI
FRAMEWORK
WD-RUNTIME
By logs i got information that
'File is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Note: I am trying to setup nwdi track for CE developments and following this [Document|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f?quicklink=index&overridelayout=true]
Following .SCA files are imported successfully
SAPBUILDT
SAPJEE
SAPJTECHS
Please help me to resolve this issue.
Thanks in anticipation.
Mandeep VirkHi John,
Following are the log details
20100309050525 Info :Starting Step CBS-make at 2010-03-09 05:05:25.0359 -6:00
20100309050526 Info :wait until CBS queue of buildspace D01_Demo_D is completely processed, before starting the import
20100309050526 Info :CBS queue of buildspace D01_Demo_D is completely processed. Starting the import now.
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/base.tools.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/com.sap.base.technology.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/deploy.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.j2ee14.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.lm.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.migration.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcbljcoapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcblvsiapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjeappconfigurationapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjecrossapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebcontainerpublic~api.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebservicesapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebserviceslib.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/webservices.lib.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
20100309050611 Info :=================================================================
20100309050611 Info :buildspace = D01_Demo_D build request id = 23
20100309050611 Info :wait until CBS queue of buildspace D01_Demo_D is completely processed, before asking for build results
20100309050611 Info :waiting for CBS queue activity
20100309050641 Info :build process already running: waiting for another period of 30000 ms
20100309050641 Info :CBS queue of buildspace D01_Demo_D is completely processed. Asking for build results now.
20100309050641 Fatal :processing of build request is not finished successfully, final status is:FAILED (more details in CBS log )
20100309050641 Info :no confirmation of request 23 because the status is not 'succeeded'
20100309050641 Info :=================================================================
20100309050641 Info :Remove software component ENGFACADE from further processing, because archive import failed
20100309050641 Info :Step CBS-make ended with result 'error' at 2010-03-09 05:06:41.0702 -6:00
- Mandeep Virk
Maybe you are looking for
-
CUCM Upgradign from cucm 7.1.3-3000-1 to cucm 8.6.2-2000-2
Dear All, I am doing upgrade from CUCM 7.1.3 to 8.6.2. COP file is successfully installed. CUCM 7.1.3 is installed on cisco UCS c200 series OS is ESXI with 4GB memory and 80GB Hard Disk. When it installing CUCM 8.6.2 database it provide a screen with
-
Problems with flash photogallery xml
Hello, I need help. I have bought your photogallery template and i am having problems with it. When i test the gallery on my portfolio website (html) all it comes up is the background, the pictures and thumbnail pictures wont load. I am putting the f
-
Calling multiple DLL from Java and calling same native method
i have two dll files named DLL_1.dll and DLL_2.dll . Both of them contain a native method which has a signature JNIEXPORT void JNICALL Java_Database_Notify (JNIEnv *, jclass); This method is common to both the DLL Now i load both of the DLL's using,
-
Need suggestion to Hide a region using SPEL.
Hi, I want to hide 'Related Details' region(Header) from notification page if the workflow notification is a 'FYI' message. How to do this in Standard page? can we do this using personalization? Please suggest me. Thanks & Regards, Sagarika
-
Is there a maximum number of small mp3 files that can be in a single flash file
my flash program fails to respond after adding one more mp3 file to the mix. Is there a maximum number of files it accepts? I have tested the mp3 file on a new fla file and there is nothing wrong with it.