ERROR running PLANNING CALENDAR JOB on DBACOCKPIT

Hi Master,
I have some problems with my dbacockpit, I cannot run any job planning calendar on dbacockpit..anyone can help me to resolved the problem?
Thanx,
Luki

Hi Luku
did you performed "self-Monitoring" and applied the master note with SNOTE?
Sem

Similar Messages

Errors running SQL Agent Jobs for 64 bit SSIS packages on a 64 bit server, but Source server 32 bit

Hi,
I can able ran the SSIS package in BIDS, since set to false in Run64BitRuntime property.
Then I created SQL server Agent job I tried the following ways
Step 1:
Type is set as SQL Server Integration Services Packages,
Run as - SQL Server Agent Service Account
Package source - FileSystem
then Execution option tab I selected 32 bit runtime
and then run the job I am getting the below error
Message
Executed as user: CIT\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 7:29:17 AM Error: 2013-11-28
07:29:18.57     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 07:29:18.57
Code: 0xC0014009     Source: Imports20_OAC_Gifts Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the
database server. End Error Error: 2013-11-28 07:29:18.59     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection
manager DataSource.DataExtract failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 07:29:18.59
Code: 0xC0047017     Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-2
Step 2:
Type - Operating sytem (CmdExec)
Run as - Sql Server agent service account
Command - C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe /FILE "D:\Example\Example.dtsx" /x86 /CHECKPOINTING OFF /REPORTING E
then run the job I am getting the below error
Message
Executed as user: MIS\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 6:37:58 AM Error: 2013-11-28
06:37:58.94     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 06:37:58.96
Code: 0xC0014009     Source: Example Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.
End Error Error: 2013-11-28 06:37:59.01     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection manager DataSource.DataExtract
failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 06:37:59.07     Code: 0xC0047017
Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-28 06:37:59.12     Code: 0xC004700C
Source: DFT_Example SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2013-11-28 06:37:59.16     Code: 0xC0024107     Source: DFT_Example
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1).Started: 6:37:58 AM Finished: 6:37:59 AM Elapsed: 1.373 seconds. Process Exit Code 1.
The step failed.
Note:
My source server is 32 bit and development environment in 64 bit
if anybody have idea please share your knowledge

Hi BIRam,
Based on the current information, the issue may be caused by the factor that the SQL Server Agent Service Account doesn’t have access to the MySQL server. Try to create a SQL Server Agent Proxy account that has sufficient permission on the MySQL server.
In addition, also pay attention to the package protection level setting.
For more information, please see:
http://social.technet.microsoft.com/Forums/sqlserver/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job?forum=sqlintegrationservices.
Regards,
Mike Yin
TechNet Community Support

Error while executing a job via dbacockpit

Hi,
I encountered the below errores while trying to execute a dba job (cleanup log, backup redo log...)
What could be the cause ? Could it be the SAPPROD_00 windows service that's not working ?
Please advise. TIA !
SAP-Basis System: Operating system call        connect failed (error no. 10061)
SAP-Basis System: Communication error, CPIC return code 017, SAP return code 236
SAP-Basis System: > CPI-C function: CMINIT(SAP)
Background processing: Error1005 when executing external command brconnect on SAPXPG_DBDEST_BELLSERVER (in=R,out=M,err=M,trc=0,trm=C. strtstat=,xpgid=0,convid=. msg:Error when openi                                               )

Hi,
If CI & DB are on different host this error normally occures.SAP return codes 236 means no connection to gateway, can you check it?
Also check whether TCP/IP RFC connection SAPXPG_DBDEST_* is working fine or not.If it is not working fine then please check whether you have mentioned below details
Program              sapxpg
Target Host          DB Host name
Gateway Host    DB host/gateway host
Gateway service sapgw##
Also refer SAP Note 108777 - CCMS: Message 'SAPXPG failed for BRTOOLS' & Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13
Hope this helps.
Thanks,
Sushil

"Error determining planning periods for calendar " when running a program

Hi,
When i am running a program with date range say "01/05/2011" to "30/06/2011",the program is executing successfully without any error. When i am executing the same program with date range as a) "01/05/2009" to "30/06/2011" and b)"01/05/2008" to "30/06/2011" the program is failing with error as "Error determining planning periods for calendar". Can anyone suggest me what i should do to avoid the failure of the program with above date ranges also.
Thanks in advance,

Dear,
Error message 61123:"Error determining planning periods for calendar &".The PPC planning calendar specified in the material master MRP 2 view for the material is incorrectly.
The planning calendar periods are insufficiently maintained for the planning calendar used.
Check the period of planning calendar in MD26 and generate the correct period.You can avoid the problem in several ways:
Maintain the planning calendar far enough in the future (at least until beyond the end of the planning horizon).
Also check any demand is lies beyond the validity period of planning calendar.
Reduction of the planning horizon of MRP also can control such issue, as MRP planning horizon lies in an area in which the planning calendar is no longer maintained
Regards,
R.Brahmankar

An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))

We are using DPM Version: 4.1.3465.0 with System Center 2012 Service Pack 1 to back up VMs in our Hyper V Cluster. We have a total of 37 VMs with a combination of 2008r2 servers and 2012 servers. One of our 2012 servers will not backup, and we consistently
get the message "An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))". I have seen this error message when I Googled it, but cannot get past it. I have deleted the Protection Group and
data and tried to re-create, but get the same errors. I also thought the the server might be mis-reporting the data size, but I expanded that to cover the replication data. I have also tried to perform consistancy checks multiple times with no luck. I have
not seen a difinitive answer from my Google searches, so was hopeful someone has seen this also, and have had success in resolving. Currently this server has no backup recovery points, so I am worried if it does crash. I think I have the rollups installed
as well.

Hi Kelly,
does the issue still persists?

APO Planning Calendar error /SAPAPO/CAL404

Hello friends, I am working in the transaction /sapapo/calendar trying to change a Planning Calendar and when I try to Calculate the periods in the view "Calculation Rule" i got a error message saying: Factory calendar TU not found (message number /SAPAPO/CAL404).
I have looked into SCAL transaction and the factory calendar is OK created and valid.
Thank you very much in advance.
Regards.
Ricardo Pereira

Hello Senthil,
Thank you for your help!!
In the Time Stream I have changed the field Factory Calendar for another one for testing and it worked well, I mean I could caculate the periods using another calendar. Comparing both It's all the same there is no difference beteween them.
But when I put the one that I really have to use (the correct one) in the time stream it gives the message Calendar not found. Although it exists and appears in the match code and If I get in the SCAL in APO as well as in R/3 I can edit it.
I have checked the calendar parameters in SCAL and also the time zone including in one of the locations that use this time stream and it's all fine.
Do you have any other idea?
:O(
Thank you very much indeed.
Regards.
Ricardo

An unexpected error occurred while the job was running. (ID: 104)

I'm getting this error in the event logs when trying to run a consistency check / sync with one of our file servers.
This server was working fine, but w needed to migrate the data to a new partition (GPT) to allow it to expand past the 2TB limit of MBR partitions. I added a new 3TB disk migrated the data and changed the drive letter to what the old partition was
prior. Since then we seem to get this error.
I have installed the update roll up on both the server and the agent side. I have also removed the server from the protection group then re-added it. I've also removed and reinstalled the agent on the file server.
Any help is appreciated! Here's the full error from the DPM server:
The replica of E:\ on server is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
An unexpected error occurred while the job was running. (ID: 104)

Server Version is Windows 2012 R2 STD. DPM is 4.2.1235.0 (DPM 2012 R2). I expanded the production file server. All that server does is host up file shares.
I suspected the fact that I created a new volume and changed drive letter back to the original to be the source cause of the issue. What I ended up doing is blowing away the backups from this server on disk and re-adding it to the protection group.
It now runs much longer, but still times out at random with the error mentioned above.
Vijay: The error was copied from Event Viewer. Not sure what else you require? Event ID is 3106 from DPM-EM.
The DPM logs say:
Affected area: E:\
Occurred since: 2015-01-05 2:04:38 AM
Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery
points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))
Date inactivated: 2015-01-05 7:03:04 AM
Recommended action: No action is required because this alert is inactive.
Affected area: E:\
Occurred since: 2015-01-05 2:04:38 AM
Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing
recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))

An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057)) After DPM 2012 SP1 to R2 Upgrade

Hi,
We have upgraded DPM 2012 SP1 to DPM 2012 R2 and OS is Windows 2012 standard.
Now in File Protection Group, we receive error
"An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))".
This happens to only one Drive(X: Drive) of the PG server, other drive(Z: Drive) backup is working fine.
We tried,
Deleted entire protection group and recreated ,
Ran consistency job 2 to 3 times.
Ran Synchronize with consistency check.
But every time It failed. Before upgrade it was working fine.
Thanks

Hi
I would suggest opening a new case with MS to allow the DPM team to further look into the issue. Also the DPM 2012 R2 RollUp which addresses the (0x80070057)
issue is Rollup 1 and the private will not be needed after applying Rollup 1. The Roll up is found here
http://support.microsoft.com/kb/2904687/en-us
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your
question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

Error determining planning periods for calendar

Hello SAP Guru's
We are receiving the above error when trying to go into MD04 for a particular material. we have checked the forecast agains the planning calendar and the dates in the forecast and demand planning are approximately 2 years less than the end date in the planning calendar.
Checking SAP it has said to extend the planing calendar past the planning horizon. It is already extended past the planning horizon.
The only issue with this product is that the material will soon be superseded by another material, this has a different calendar assigned to it. Could this be the problem?
Any info gratefully received.
Thanks
Sue

Hello Vicky,
The error occurs when first going into MD04. The exact error message is as follows:
Error determining planning periods for calendar M14
Message no. 61123
Diagnosis
The system could not determine sufficient planning periods by the planning calendar to group requirements by planning calendar periods for all the requirements planned in the future.
System Response
When a material is planned by using the periodical lot size by planning calendar, sufficient periods must be calculated to group requirements by the planning calendar for all requirements.
Procedure
Rework the planning calendar with which the material was planned, which means calculate new planning calendar periods.
To do this, go to Customizing for MRP, under the activity Change PPC periods.

Read Error logs after running the background jobs

Hi,
How to read the error logs after running the background jobs. In our scenarion we are running the COHV transaction to release the production orders in background. But we are not finding the error logs after background job. We would like to read the error logs and correct for further processing.
Kindly suggest.
Thanks & Regards,
N. Laxman

Hi
you can check the back ground jobs defined by any user in SM37 and where you can see the spool and job logs as well.
plz check in your case and revert back
Regards
Anupam Sharma

DBA Cockpit: Planning calendar and remote Oracle databases- which method?

For using DBA Planning Calendar to schedule BR*Tools for remote Oracle database AS Java systems I have successfully implemented both the Secure Shell and SAP gateway methods in [Note 1025707 - DBA Cockpit: Planning calendar and remote Oracle databases|https://service.sap.com/sap/support/notes/1025707] and was interested in which of these two methods others have found to be more supportable and maintainable?
In more detail, the note has these two methods for non-ABAP remote systems:
2. Connection through Remote/Secure Shell
Specifically Secure Shell. Rejecting remote shell as too old and insecure a protocol.
3 Connection through SAP gateway
The note provides clues as to how these methods work. Expanding on that:
With #2, central ABAP system calls out to its OS user level to execute the ssh client (after gw/rem_start has been set to the non-default value SSH_SHELL) which it finds in the location specified in gw/ssh (default value is /usr/bin/ssh). It must use password-less authentication and the key-based authentication must also not require a passphrase. (Using ssh-agent is not an option since this is being called from SAP, not from your own script.)
It remotely runs via ssh a command, sapxpg, which must be found in the PATH of the remote user. (This is why the note, which has you place this exe sapxpg and a subset of the BR*Tools in the home dir of the remote user, also has you make sure the home dir is included in the path--your OS might or might not include the user's home dir in the path in the default shell environment for a new user.)
Then via sapxpg, the BR*Tools are invoked.
One thing that may be confusing here is you have to check at least one gateway parameter 'gw/...' in the central system to get the method #2 the non-gateway method to work--this is because the two methods are technically almost the same: in #2, secure shell is used to basically start a gateway on the fly with sapxpg in order to call the BR*Tools each time a DBA Planning Calendar action runs or you view DBA or Backup logs of the remote system from the central system. With #3, the gateway runs continuously on the remote system.
With #3, central system connects to remote SAP standalone gateway, which executes the BR*Tools installed in the standard SAP kernel directory of the SAP gateway. This method is simpler to describe so it sounds like it has less components than the secure shell method, however you do have an entire SAP system running, although it is just a standalone gateway.
Thoughts:
These pros/cons are UNIX/Linux-oriented since I assume most Windows environments do not have added 3rd-party products that provide secure shell so SAP gateway is the only method.
Secure shell
+ Less software required (not counting secure shell which comes with the operating system distribution): just a few SAP executables placed in the home dir of an ordinary user on the remote system.
+ Secure shell service probably automatically starts upon boot of the remote system operating system.
+ Secure shell is a widely used tool outside of SAP for executing commands remotely without passwords.
- Installation is non-standard: shell environment of remote user is not adapted by SAP installer since SAP installer is not used, SAP executables in the home dir of the remote user is non-standard. Has to be setup manually.
- Requires setting up secure shell key-based authentication, which should be known by UNIX/Linux admins or combined Basis/UNIX/Linux admins, but might be less familiar to SAP Web AS only admins.
- If your admin config policy is to have SAP interact as little possible with the OS level for interfaces with other systems, here you are relying on the OS-level secure shell.
- Using a private key that does not require a passphrase on the central system may not fit with your security policies if you have standards for secure shell configuration.
SAP gateway
+ The gateway is a standard installation, performed with SAP installation tool, with the exception of a few additional environment settings that have to be added after the installation. BR*Tools are installed in the standard location. Can use standard procedures for updating this software.
+ Only uses SAP software.
- More software on remote system: standalone gateway just to run BR*Tools and view logs.
- SAP Kernel of remote gateway should probably be updated whenever you do SAP kernel updates across your systems for consistency. One more system to update.
- Shell environment of remote user that runs the gateway looks like something setup by the SAP installer but is not standard because it has a few additional environment variables added.
- Need to make sure the SAP gateway is started on the remote system.

Hi Joe,
I configured a monitoring/dba landscape for two SAP Portals and one SAP BusinessObjects system on a SAP landscape by using DBACOCKPIT, at a customer site. These systems are running on AIX, Windows 2003/2008 servers and attached to the central monitoring system with standalone SAP gateway installations.
One another reason to not use OS based commands or 3rd party tools is security. We are stopping and disabling most of the services on OS where SAP system is running on, because of the security reasons. I faced more security gaps on rsh/ssh and the other tools than standalone SAP Gateway installations. As you can figure out that rsh/ssh is getting more attack than standalone SAP Gateway, because of well known by the IT world.
As a summary of it, this depends to point of view and policy of the IT organization. I applied both ssh and standalone SAP Gateway solutions at my customers, but I choose standalone SAP Gateway installation among of them.
Best regards,
Orkun Gedik

Error Reading Planning Area

Hello Gurus,
While executing a macro via an activity on a background job, the job is cancelled with an error message Error Reading Planning Area. Macro is calculating certain Key figure
We then run Consistency Check for planning area but no inconsistency and errors were found. We also check the macro and it is on GREEN LIGHT status. We reexecute but it still fails.
Kindly help on how to go abaout this error as we need this macro working.
This job with the macro is working for quite a long time and it is the first time it fails and encountered the said error.
Any help will be gladly appreciated.
Thanks in advance,
Raymond

Check your planning area and see if it has been initialized to the right dates. Its possible your planning book and macros are reading a differenty date and the planning area is not initialized till that date
Check your macros in the macro workbench (/sapapo/advm) to see what dates are on the macros. If you run the macro interactively you should be getting the same error
reinitialize the planning area.. pl search the forum for some recent posts on the program involved
Also check when your planning area was initialized last. you might have to set the initialization requently based on your planning books and other processes

Error while scheduling Background Job for User/Role Full Synchronization

Hi all,
We have installed RAR 5.3 Component and uploaded the authorization data & established the connectors to the backend system.
We have performed all the post installation activities and everything is complete.
When we have scheduled User -Full Synchronization with the Back End system as a part of Post Installation Activity we are receiving the below error message
"Error while executing the Job:Cannot assign an empty string to host variable 2."
Also the VIEW LOG/ Terminate Job buttons are disabled in this screen.
Can somebody please help us in resolving the above issue
Thanks and Best Regards,
Srihari.K

Hi,
We are copy pasting the error log (Part as it is huge) below here. We could able to do Full Synch for Roles and also for Profiles. Only for User Synch we are getting this error and none of the users are sychronized to RAR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WILSONA of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WINDC of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WLADICHJ of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user WUK of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user ZENGS of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: Update user ZHENGL of HL2-QAHR
Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
INFO: All System Flag:false=====Last Batch Flag:true
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis loadUserData
INFO: @@@ User sync completed for params true: Syskey List is [HL2-QAHR]
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob run
WARNING: *** Job Exception: Cannot assign an empty string to host variable 2.
com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 2.
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
     at com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:57)
     at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)
     at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)
     at com.virsa.cscext.dao.CSCDAO.updateIgnoredUserData(CSCDAO.java:1388)
     at com.virsa.cscext.dao.CSCDAO.populateGenObjUser(CSCDAO.java:1169)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.populateGenObj(BatchRiskAnalysis.java:868)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.insertBAPIUserData(BatchRiskAnalysis.java:142)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.loadUserData(BatchRiskAnalysis.java:390)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1275)
     at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
     at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
     at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
     at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     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:319)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 13 Status: Error
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job:Cannot assign an empty string to host variable 2.
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=13, status=2, message=Error while executing the Job:Cannot assign an empty string to host variable 2.
Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Complted Job =>13----
Please let us know how to resolve this error
Thanks and Best Regards,
Srihari.K

Internal error occurs in background job scheduling

Hi Experts,
We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
Please find the following observation on our side on this message.
1) This message is not coming for only one report not for others.
2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
3) Persons having SE38 auhtorization are able to run this report.
Please advise.
Thanks in advance,
Viven

What is the message ID and number? Have you tried OSS search and debugging?
What does this program do, in a nutshell?

Error while adding a job to scheduler

Hello,
I have a batch job that is running fine in both DEV and QA environment. In DEV, I am able to schedule and run it daily. I created a similar schedule in QA environment using BODS Mgmt Console/Administrator. However, upon Activating the schedule, I am getting the following error message. Would someone know why would this error be thrown and steps to troubleshoot this error?
Thanks.
[Repository:AECON_DW_REPOSITORY Schedule:Daily_Run_QA Error:Error while adding a job to scheduler]
When contacting the server above exception was encountered, so it will be assumed the schedule is not active anymore.

Hi Rizwan Tahir ,
Delete the job server associated with the current batch job and recreate it.
Then try creating a new schedule using the new job server.
And take care that job server is created in QA environment.
Hope this should work.
Regards,

ERROR running PLANNING CALENDAR JOB on DBACOCKPIT

Similar Messages

Maybe you are looking for