Job SAP_COLLECTOR_FOR_PERFMONITOR failing in alternate hours

Hello All,
The job SAP_COLLECTOR_FOR_PERFMONITOR in solution manager 7.1 was running fine till last week but now it is failing. Every alternate job fails.
Checked logs and it states error message:
SQL error 1-: Function sequence error
Checked system logs:
After the attempt to call a database operation, the database system has
returned the error code specified in the message, which indicates that
the operation concerned could not be executed successfully.
Can someone suggest and provide some input to correct this.
Regards,
Mohit

Hello Divyanshu,
Here is the job logs
Date       Time     Message text                                                                Message class Message no. Message type
26.08.2014 00:13:03 Job started                                                                      00           516          S
26.08.2014 00:13:03 Step 001 started (program RSCOLL00, variant , user ID SOLMAN_BTC)                00           550          S
26.08.2014 00:13:09 Clean_Plan:Bereinigung der DB13-Einplanungen                                    DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:started by RSDBPREV                       on server FR105     DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZZZ      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System BWP00002 werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System BWT      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System DEV      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System KON      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System PRD      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZD1      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZD200001 werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZE1      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZP1      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZP2      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZQ1      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZQ2      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:Jobs in System ZSM      werden bereinigt                             DB6PM         000          S
26.08.2014 00:13:09 Clean_Plan:finished                                                             DB6PM         000          S
26.08.2014 00:21:42 SQL error 1-: Function sequence error                                           0Q           029          E
26.08.2014 00:21:42 Job cancelled after system exception ERROR_MESSAGE                               00           564          A
werden bereinigt means: Adjusted
Regards,
Mohit

Similar Messages

DDIC job 'SAP_COLLECTOR_FOR_PERFMONITOR' fail 2 times daily

Hi Gurus,
we have an issue with DDIC job 'SAP_COLLECTOR_FOR_PERFMONITOR'.
this job daily fails at 08am and 10pm of system time throwing ST22 dump.
DDIC job log is 'Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Database system not supported
ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
Job cancelled
ST22 runtime Runtime error 'TSV_TNEW_PAGE_ALLOC_FAILED' occurred for users 'DDIC'.
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          06/17/2009 20:07:11
Short text
No more storage space available for extending an internal table.
What happened?
     You attempted to extend an internal table, but the required space was
     not available.
ECC6.0,Kernel700,patch 185,oracle 10.2.0.4.0
regards
nag

Hi,
Check this note "Note 945279 - Workload Collector terminates due to memory problems"
With Regards,
Saurabh

Job SAP_COLLECTOR_FOR_PERFMONITOR canceled

Good evening everybody,
The job SAP_COLLECTOR_FOR_PERFMONITOR is being canceled hourly with the log below:
                                                                                Date       Time     Message text                                                  Message class Message no. Message type
04.08.2009 15:30:55 Job started                                                        00           516          S
04.08.2009 15:30:55 Step 001 started (program RSCOLL00, variant , user name DDIC)      00           550          S
04.08.2009 15:30:57 ABAP/4 processor: CONVT_OVERFLOW                                   00           671          A
04.08.2009 15:30:57 Job cancelled                                                      00           518          A
The dump generated in the ST22 is CONVT_OVERFLOW
Overflow when converting from 15362394
What happened?
The current ABAP/4 program "RSHOST2M " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Everyone can help me to solve this issue? Our SAP version is R/3 4.6C.
Best Regards,
Fábio Karnik Tchobnian

Dear Friend,
Thanks for your help.
I apllied the part below from the note 903220
To remove the corrupted data in table MONI:
1. Call transaction ST03
2. With Goto -> Performance database -> Contents of Database
3. Select entry you want to delete
4. Further info will be '** delete**'
5. Confirm the delete
05.08.2009 Page 2 of 2
SAP Note 903220 - Short dumps CONVT_OVERFLOW in RSHOSTDB
or RSHOST2M
A sufficient way to find out which entries to delete would be:
- check when the short dump occured first
- delete the OS entries from MONI since the day before the first
short dump occured
The job SAP_COLLECTOR_FOR_PERFFMONITOR now is not being canceled anymore , however it is happening the same dump dump from a differente program after the job is finished as the log below from the ST22
ABAP runtime errors    CONVT_OVERFLOW
       Occurred on     05.08.2009 at 15:50:38
Overflow when converting from "-3.10504e+231"
What happened?
The current ABAP/4 program "SAPLSTUW " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
When attempting to convert the value "-3.10504e+231",
an overflow occurred.
Do you have some advice?
Best Regards
Fábio Karnik Tchobnian:

SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND

Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.

Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text                                                                                        |
|    Program "RSORA811" not found.                                                                 |
|What happened?                                                                                    |
|    There are several possibilities:                                                              |
|                                                                                                  |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|    or                                                                                            |
|    Error in the SAP kernel.                                                                      |
|                                                                                                  |
|    The current ABAP "RSCOLL00" program had to be terminated because the                          |
|    ABAP processor detected an internal system error.                                             |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    On account of a branch in the program                                                         |
|    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                              |
|    or a transaction call, another ABAP/4 program                                                 |
|    is to be loaded, namely "RSORA811".                                                           |
|                                                                                                  |
|    However, program "RSORA811" does not exist in the library.                                    |
|                                                                                                  |
|    Possible reasons:                                                                             |
|    a) Wrong program name specified in an external PERFORM or                                     |
|       SUBMIT or, when defining a new transaction, a new                                          |
|       dialog module or a new function module.                                                    |
|    b) Transport error                                                                            |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
|     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
|    The main program was "RSCOLL00 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 535                                 |
|    of the (Include) program "RSCOLL00".                                                          |
|    The program "RSCOLL00" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. " bharath"                                                                       |
|    Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.

SAP_COLLECTOR_FOR_PERFMONITOR failing with dump

HI All,
SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR is failing with below job log
31.05.2012 00:19:03 Job started
31.05.2012 00:19:03 Step 001 started (program RSCOLL00, variant , user ID CP1SUP)
31.05.2012 00:19:06 Clean_Plan:Cleanup of DB13 Plannings
31.05.2012 00:19:06 Clean_Plan:started by RSDBPREV on server ttahmsv2050
31.05.2012 00:19:06 Clean_Plan:Cleaning up jobs of system PRD
31.05.2012 00:19:06 You are not authorized for DB access (S_DBCON: <LOCAL SYSTEM> PRD <Windows authentication> 03)
31.05.2012 00:19:06 Function DB6_PLAN_STOP_BATCH_JOB failed with return code = Job error
31.05.2012 00:19:06 Clean_Plan:terminated with error
31.05.2012 00:19:06 REASON=Job error
31.05.2012 00:19:06 ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW
31.05.2012 00:19:06 Job cancelled
and its also getting finished with job log
31.05.2012 01:19:03 Job started
31.05.2012 01:19:03 Step 001 started (program RSCOLL00, variant , user ID CP1SUP)
31.05.2012 01:19:06 Database system not supported
31.05.2012 01:19:06 Database system not supported
31.05.2012 01:19:11 Job finished
i.e every alternate run it gets finsihed and gets cancelled
Dump obtained is COMPUTE_INT_TIMES_OVERFLOW
I have found this note 1027512 not sure if there is any other way

Hi,
thank you all for your help. I tried the solution provided in SAP Note 199586. Although, it does not talk about my specific issue, however, I tried solution 1 and after that job is running fine.
Thanks again for all your help.
Regards,
Sudhir

Job    SAP_COLLECTOR_FOR_PERFMONITOR getting delay.

Hi Friends,
In one of my customer system, the job    SAP_COLLECTOR_FOR_PERFMONITOR is getting delay on particular time.
Normally every hour it is getting finished with 5 to 40 secs.
But at a particular the job starts at i.e. 02:26am is finishing successfully but taking much time. It's nearly taking 37,000 secs.
Job log:
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Job finished
My system details are:
Comp version :BBPCRM 4.0
Database system: ORACLE , 10.2.0.4.0.
Kernel release :   640
SAP_BASIS:SAPKB62063
I can submit if any information required. Earlier solution is much aspirated.
Regards
Sudhakar

Sorry Guys I was not well to answer your replies.
Thanks for your replies.
Still the issues persists. Here are some more information which would help you to help me.
I have checked BTC are available.
In SM51 one BTC is running for long time for this with a entry of u201CSAPLSTUW   000 DDICu201D
& Daily BTC process is Disconnecting from oracle at 2 Ou2019clk then this job is taking that BTC. Is there any relation between this?
Wed Oct 6 01:50:01 2010
got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
Client NLS settings:
Logon as OPS$-user to get SAPCRM's password
Connecting as /@SID on connection 1 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
   0 UTF8                                                      1 0x114876050 0x114888db0 0x114888668
Starting user session (con_hdl=1,svchp=0x1160b89c8,srvhp=0x11488bd68,usrhp=0x1160b85b0)
Now '/@SID' is connected: con_hdl=1, nls_hdl=0, session_id=687.
Got SAPCRM's password from OPS$-user
Disconnecting from connection 1 ...
Close user session (con_hdl=1,svchp=0x1160b89c8,usrhp=0x1160b85b0)
Now I'm disconnected from ORACLE
Connecting as SAPCRM/<pwd>@SID on connection 1 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
   0 UTF8                                                      1 0x114876050 0x114888db0 0x114888668
Starting user session (con_hdl=1,svchp=0x1160b89c8,srvhp=0x11488bd68,usrhp=0x1160b85b0)
Now 'SAPCRM/<pwd>@SID' is connected: con_hdl=1, nls_hdl=0, session_id=687.
Connection 1 opened (DBSL handle 1)
Wp Hdl ConName          ConId     ConState     TX PRM RCT TIM MAX OPT Date     Time   DBHost
134 000 R/3              000000000 ACTIVE       NO YES NO 000 255 255 20100930 152615 host05
134 001 R/3*WORKFLOWTRAC 134000057 ACTIVE       NO NO NO 004 255 255 20101006 015001 host05
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c       2220]
Wed Oct 6 02:08:47 2010
Disconnecting from connection 1 ...
Close user session (con_hdl=1,svchp=0x1160b89c8,usrhp=0x1160b85b0)
Now I'm disconnected from ORACLE
Disconnected from connection con_da={R/3*WORKFLOWTRACE,134000057,1}
Job is taking much time to finish at 02:26 with a lock entry in MONI table. In ST03n sometimes 3:26 job is showing error but it is not failing.
Error log:
System name                            Host name                        Report   Date       End time
Error message
Host05_SID_00                       Host05                        RSCUECRM 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSHOSTDB 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSORACOL 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSORAHCL 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSRFCDLT 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSRFCDMN 06.10.2010 03:26:01
Host05_SID_00                       Host05                        RSSTAT60 06.10.2010 03:26:06
Table MONI is locked by user DDIC
Host05_SID_00                       Host05                        RSSTAT87 06.10.2010 03:26:06
Host05a_SID_01                      Host05a                       RSHOSTDB 06.10.2010 03:26:07
Host05a_SID_01                      Host05a                       RSRFCDMN 06.10.2010 03:26:07
Host05_SID_00                       Host05                        RSSTAT83 06.10.2010 03:26:11
Begin error recovery:
Host05_SID_00                       Host05                        RSSTAT60 06.10.2010 03:27:16
Table MONI is locked by user DDIC
Contents of TCOLL
Report      Days of Week                                   Hours of Day                                Repe-    System
                                                                                titions
         Mo    We    Fr    Su 0     2     4     6     8    10    12    14    16    18    20    22
RSCUECRM X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSDBPREV X X X X X X X X     X     X     X     X     X X X     X     X     X     X     X        1         C
RSDB_PAR X X X X X X X                          X              X                 X                 1         C
RSDB_TDB X X X X X X X                       X                                      X              1         C
RSDB_WDB                    X                                      X                                      1         C
RSHOSTDB X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         *
RSHOSTDC X X X X X X X X     X     X     X     X     X     X     X     X     X     X     X        1         C
RSHOSTPH X X X X X X X                             X        X                    X                 1         *
RSORA811 X X X X X X X                                      X                    X                 1         C
RSORACOL X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSORAHCL X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSRFCDLT X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSRFCDMN X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         *
RSSDBDLY X X X X X X X     X                                                                       1         C
RSSTAT60 X X X X X X X           X        X        X     X        X     X        X        X        1         C
RSSTAT83 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSSTAT87 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X     1         C
RSSTAT90 X X X X X X X                                         X                 X                 1         *
RSSTAT98 X X X X X X X              X        X        X        X        X        X                 1         *
RSSTATPH X X X X X X X                             X        X                 X                    1         *
RSTUNE80 X X X X X X X                             X              X                          X     1         *
RSXRPM          X                             X                                                           1         C

Job SAP_COLLECTOR_FOR_PERFMONITOR keep on running

Dear All,
I am facing problem in prd ,we have 2 active node the job SAP_COLLECTOR_FOR_PERFMONITOR keep on running eg   44,21sec,tan I have to cancel it manual this is suddenly. this happened with not all the hourly jobs ,but only 1 or 2 time in a day a any time.
Please find the below . Please suggest how to solved it
We are using ECC6 on oracle 10g
25     BGD     1696     Running          Yes     4               2     SWNCTOTAL     000     DDIC     Insert     SWNCMONI
Sm37 log
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server nodea
Clean_Plan:Cleaning up jobs of system PRD
Clean_Plan:finished
Database destination not found
Cannot determine operating system data for database
kind regards,
kumar

Dear Sunny
Thanks for you suggestion , no it happened any time and there is sufficient no of background process are free
I have see it stuck in table SWNCMONI while Insert ans i have checked the snote .Please suggest
sm21 log
Time     Type Nr Clt User        TCode Priority Grp N Text
04:51:46 DIA 001 100 BASIS               AB 0 Run-time error "TIME_OUT" occurred
04:51:46 DIA 001 100 BASIS               AB 1 > Short dump "101021 045146 clusa " generated
04:51:46 DIA 001 100 BASIS               D0 1 Transaction Canceled SY 002 ( Time limit exceeded. )
05:01:04 RD                                      Q0 I Operating system call connect failed (error no. 10061)
05:01:45 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:01:45 DIA 000 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:01:45 DIA 000 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:20:11 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:20:11 DIA 001 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:20:11 DIA 001 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:20:24 RD                                      Q0 I Operating system call connect failed (error no. 10061)
05:21:18 RD                                      Q0 I Operating system call connect failed (error no. 10060)
05:21:18 DIA 001 100 BASIS               R4 9 Communication error, CPIC return code 017, SAP return code 236
05:21:18 DIA 001 100 BASIS               R6 4 > CPI-C function: CMINIT(SAP)
05:22:56 RD                                      Q0 I Operating system call recv failed (error no. 10054)
08:46:50 BTC 025 000 DDIC                       BY 4 Database error 24909 at UPD access to table TST01
08:46:50 BTC 025 000 DDIC                       F6 H Database error: TemSe->XRTAB(3)->1 for table TST01 key
08:46:56 RD                                      Q0 I Operating system call recv failed (error no. 10054)
08:47:11 BTC 025 000 DDIC                       F3 T Invalid object name for TemSe object: " "
08:47:13 BTC 025 000 DDIC                       EC F Failed to create log for job SAP_COLLECTOR_FOR_PERFMONITOR 19301600 %NEWSTEP/
08:47:13 BTC 025 000 DDIC                       F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:47:13 BTC 025 000 DDIC                       R4 7 Delete session 001 after error 023
09:38:51 DP                                      Q0 I Operating system call recv failed (error no. 10054)
09:38:51 DP                                      Q0 4 Connection to user 9850 ( ), terminal 90 (233 ) lost
10:00:24 RD                                      Q0 I Operating system call recv failed (error no. 10054)
10:00:24 RD                                      S2 3 Connection to CPI-C client 101 was closed
10:00:24 DIA 001 100 PORTAL                R4 9 Communication error, CPIC return code 020, SAP return code 223
10:00:24 DIA 001 100 PORTAL                R5 A > Conversation ID: 909935
10:00:24 DIA 001 100 PORTAL                R6 4 > CPI-C function: CMSEND(SAP)
10:26:36 DP                                      Q0 I Operating system call recv failed (error no. 10
and just now the sm37 log is different
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system PRD
Clean_Plan:finished
Database destination not found
Cannot determine operating system data for database
Buffer statistics for clusa transferred to MONI
Please suggest
Kind Regards,
Kumar
Edited by: kumar9 on Oct 21, 2010 12:30 PM
Edited by: kumar9 on Oct 21, 2010 2:37 PM

Reporting (Project Publish) job is failing with 'The given key was not present in the dictionary'

I am using Project Server 2010 with SQL Server 2008 R2.
I have a PWA Instance which was running fine. I have a big number of projects and I do not keep site for all the projects as we do not need project site in our business.
Everything was running fine but during last few days, some of the jobs like Reporting (Project Publish) and Reporting (Project Delete) job is failing with the same error details for all the projects. I am not able to trace where the data is wrong/corrupt
and how to resolve it.
The error detail and ULS Log is given below anod I would appreciate if someone can guide me where the problem is and suggest me any solution.
QUEUE ERROR DETAIL:
General Reporting message processor failed:
ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='4f36afe0-43dc-4143-befc-0452da416e69' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='071aeb7b-540e-45fa-b40b-a94a5d2e8e04' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='55445e77-51e3-40d8-a62f-e6db0b897444' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='3ab5a1ba-0915-45bb-a078-4b4b7c38af51' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='b27acd8f-6cde-47d4-bd53-5930e84dc940' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
ReportingProjectChangeMessageFailed (24006) - The given key was not present in the dictionary.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='b7250544-2a11-4887-8dcd-378b34b33ae1' QueueMessageBody='Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish'' Error='The given key was not present in the dictionary.'.
Queue:
GeneralQueueJobFailed (26000) - ReportingProjectPublish.ReportProjectPublishMessageEx. Details: id='26000' name='GeneralQueueJobFailed' uid='0706d212-f737-43ea-b694-c420488d57bb' JobUID='ca238fcf-d91b-46d6-a9c2-15f2cc35230d' ComputerName='WebSrv1' GroupType='ReportingProjectPublish'
MessageType='ReportProjectPublishMessageEx' MessageId='1' Stage=''. For more details, check the ULS logs on machine WebSrv1 for entries with JobUID ca238fcf-d91b-46d6-a9c2-15f2cc35230d.
ULS LOG:
Timestamp              Process
TID   Area                          Category
EventID Level     Message Correlation
01/19/2015 19:05:07.44 Microsoft.Office.Project.Server (0x1D30) 0x23FC SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=117.485513497555 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:07.66 Microsoft.Office.Project.Server (0x1D30) 0x2C94 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=192.534598230475 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:08.16 Microsoft.Office.Project.Server (0x1D30) 0x1CFC SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=448.362263674397 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:08.36 Microsoft.Office.Project.Server (0x1D30) 0x17E0 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=162.22152253546 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:09.00 Microsoft.Office.Project.Server (0x1D30) 0x0898 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=557.699412860413 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:09.36 Microsoft.Office.Project.Server (0x1D30) 0x1F20 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=253.695754010613 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:09.67 Microsoft.Office.Project.Server (0x1D30) 0x0D68 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=239.76302803952 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:10.64 Microsoft.Office.Project.Server (0x1D30) 0x3324 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=973.469925841736 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:11.92 Microsoft.Office.Project.Server (0x1D30) 0x2DB8 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=1275.5063556303 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:12.96 Microsoft.Office.Project.Server (0x1D30) 0x0A1C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=1041.55499409959 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:13.15 Microsoft.Office.Project.Server (0x1D30) 0x0518 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=133.891034879385 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:13.35 Microsoft.Office.Project.Server (0x1D30) 0x14EC SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_FULL_PUBLISH_DELETE). Execution Time=207.250205426327 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:14.69 Microsoft.Office.Project.Server (0x1D30) 0x10B4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_PUBLISH_PROJECT). Execution Time=267.137845971639 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:14.93 Microsoft.Office.Project.Server (0x1D30) 0x14E0 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureScalar -- MSP_PUBLISH_PROJECT). Execution Time=209.552772167485 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:16.10 Microsoft.Office.Project.Server (0x1D30) 0x2AB4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResultWithOutputParameters -- MSP_SRA_ValidateServerLevelSRA).
Execution Time=717.808222684698 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:16.67 Microsoft.Office.Project.Server (0x1D30) 0x2AB4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (FillTypedDataSet -- MSP_SRA_GetData). Execution Time=307.24482978413 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:17.58 Microsoft.Office.Project.Server (0x1D30) 0x2AB4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResultWithOutputParameters -- MSP_SRA_ValidateServerLevelSRA).
Execution Time=123.306566048297 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:19.12 Microsoft.Office.Project.Server (0x1D30) 0x25F4 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResult -- MSP_WEB_SP_QRY_CreateSavedTasksForProject). Execution
Time=111.699445284922 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:19.61 Microsoft.Office.Project.Server (0x1D30) 0x2AC8 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (ExecuteStoredProcedureNoResult -- MSP_WEB_SP_QRY_Statusing_BuildTaskHierarchy). Execution
Time=449.279962592357 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:19.79 Microsoft.Office.Project.Server (0x1D30) 0x26D0 Project Server Server-side Project Operations 8tci Monitorableser1 PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1,
PSI: [QUEUE] System.IO.FileNotFoundException: The site
http://epm.company.com/sites/Workspaces2/PROJECT_1 could not be found in the Web application SPWebApplication Name=SharePoint - 80.     at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken
userToken)     at Microsoft.SharePoint.SPSite..ctor(String requestUrl)     at Microsoft.Office.Project.Server.BusinessLayer.Project.OpenProjectWeb(Guid projectUid)     at Microsoft.Office.Project.Server.BusinessLayer.Project.SetPwsProperties(Guid
projectUid)     at Microsoft.Office.Project.Server.BusinessLayer.Queue.ProcessPublishMessage.ProcessMiscellaneousPublishMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:19.79 Microsoft.Office.Project.Server (0x1D30) 0x26D0 Project Server Server-side Project Operations 8tcj Monitorable PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1,
PSI: [QUEUE] MiscellaneousPublishMessage failed on project b95c52ba-bc00-4301-aab5-890d0b057c29 ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:27.42 Microsoft.Office.Project.Server (0x1D30) 0x3088 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes: Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish' The given key was not present in the dictionary. . Standard Information: PSI Entry Point:   Project User: Domain1\User1 Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d PWA Site URL:
http://epm.company.com/PWA SSP Name: SharedServices1_PsiServiceApplication PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:27.42 Microsoft.Office.Project.Server (0x1D30) 0x3088 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)
at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:28.47 Microsoft.Office.Project.Server (0x1D30) 0x31F8 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes: Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish' The given key was not present in the dictionary. . Standard Information: PSI Entry Point:   Project User: Domain1\User1 Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d PWA Site URL:
http://epm.company.com/PWA SSP Name: SharedServices1_PsiServiceApplication PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:28.47 Microsoft.Office.Project.Server (0x1D30) 0x31F8 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)
at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:29.51 Microsoft.Office.Project.Server (0x1D30) 0x2B00 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes: Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish' The given key was not present in the dictionary. . Standard Information: PSI Entry Point:   Project User: Domain1\User1 Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d PWA Site URL:
http://epm.company.com/PWA SSP Name: SharedServices1_PsiServiceApplication PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:29.51 Microsoft.Office.Project.Server (0x1D30) 0x2B00 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)
at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:30.56 Microsoft.Office.Project.Server (0x1D30) 0x1D20 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes: Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish' The given key was not present in the dictionary. . Standard Information: PSI Entry Point:   Project User: Domain1\User1 Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d PWA Site URL:
http://epm.company.com/PWA SSP Name: SharedServices1_PsiServiceApplication PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:30.56 Microsoft.Office.Project.Server (0x1D30) 0x1D20 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)
at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:31.60 Microsoft.Office.Project.Server (0x1D30) 0x2170 Project Server Reporting atwj Monitorable Error is: ReportingProjectChangeMessageFailed. Details: Attributes: Project UID='b95c52ba-bc00-4301-aab5-890d0b057c29'.
PublishType='ProjectPublish' The given key was not present in the dictionary. . Standard Information: PSI Entry Point:   Project User: Domain1\User1 Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d PWA Site URL:
http://epm.company.com/PWA SSP Name: SharedServices1_PsiServiceApplication PSError: ReportingProjectChangeMessageFailed (24006) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:31.60 Microsoft.Office.Project.Server (0x1D30) 0x2170 Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)
at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:32.66 Microsoft.Office.Project.Server (0x1D30) 0x24DC Project Server Reporting atwj Critical Standard Information:PSI Entry Point:   Project User: Domain1\User1 Correlation Id: ae078058-f794-47ca-b1ad-0834f7a07f4d
PWA Site URL: http://epm.company.com/PWA SSP Name: SharedServices1_PsiServiceApplication PSError: ReportingProjectChangeMessageFailed (24006) RDS: The request to synchronize change(s) to project Project
UID='b95c52ba-bc00-4301-aab5-890d0b057c29'. PublishType='ProjectPublish' failed. Message: 'ReportingProjectChangeMessageFailed'. Message Body: The given key was not present in the dictionary. Error:(null) ae078058-f794-47ca-b1ad-0834f7a07f4d
01/19/2015 19:05:32.66 Microsoft.Office.Project.Server (0x1D30) 0x24DC Project Server Reporting atwr High PWA:http://epm.company.com/PWA, ServiceApp:SharedServices1_PsiServiceApplication, User:Domain1\User1, PSI: [RDS] ULS
Event: ReportingProjectChangeMessageFailed was associated with exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.     at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.InitializeSprocParameterTypeData(Dictionary`2& routineParameterInfos)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal..ctor(DAL
dal, DataStoreEnum store)     at Microsoft.Office.Project.Server.DataAccessLayer.DAL.get_Reporting()     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.GetRefreshOperationStatus(MessageAreaType
messageArea)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)
at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext) ae078058-f794-47ca-b1ad-0834f7a07f4d

Without seeing the history, one possibility might be some corruption in the reporting database. Assuming that you are following best practices for SQL DB management, and this is not a DB neglect problem, then I would try to force a refresh to see if that
helps. You can do this by executing a custom field backup and then restore. Note: Do not do this during production hours. Let us know if that provides any therapy.
Gary Chefetz, MCITP, MCP, MVP msProjectExperts
Project and Project ServerFAQs
Project Server Help BLOG

Solution Manager 7.1 SP04 - Job SAP_COLLECTOR_FOR_PERFMONITOR

Dear Experts
I got an issue with some differences between what SolMan Setup did and SAP Note 966309 for TCOLL in SAP_BASIS 700 - 702 sais.
SolMan Setup creates the job SAP_COLLECTOR_FOR_PERFMONITOR with the following step in working client 001:
1 RSCOLL00             ABAP                             SOLMAN_BTC EN
According to SAP Note 966309, this job is supposed to run as user DDIC (or any other with same rights) in client 000. On top, there are a lot of differences between SAP Note 966309 and the content of TCOLL.
Would you change TCOLL according to this SAP Note or would you hang on what SolMan Setup did?
Thanks for short answer.
Regards, Michael

Michael,
This note is clear regarding the client and user:Note 16083 - Standard jobs, reorganization jobs
and this note is release independent.
If you check using RTCCTOOL you'll be able to see a recommendation regarding TCOLL:
7. [Note 12103 ]    Collectors and TCOLL
Description     Planning table TCOLL for SAP workload collectors for 700 (note 966309 )
Implementation Press the lights icon to get the detailed check log.
                Add missing entries to table TCOLL using ST03N > Expert Mode > Collector
                and Performance DB > Performance Monitor Collector > Execution Times.
                Schedule RSCOLL00 as an hourly batch job if not scheduled.
"schedule standard jobs" steps is required if the jobs are not scheduled already:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Basic+Configuration
"In the activities schedule Background jobs and standard jobs different jobs are scheduled. The Background job that are scheduled are jobs for the housekeeping of SAP Solution Manager. The standard jobs are the same jobs as the jobs scheduled in transaction SM36 --> u201EStandard Jobs" and schedules jobs for general SAP housekeeping. Please make sure that the jobs are not already scheduled in SM36 before executing this activity. "
Cheers,
Diego.

DPM 2012 R2 long backup to tape job randomly fail after installing SCCM 2012 Client

Hello,
I'm managing a two nodes 2012 R2 file server cluster that contains a 16To CSV. I'm using DPM 2012 R2 to backup this entire shared volume directly to LTO 4 tapes, the job last about 55h.
Since SCCM 2012 client has been installed(I don't manage it), the tape jobs are failing ramdomly after several hours with the error:
Type: Tape backup
Status: Failed
Description: The DPM service was unable to communicate with the protection agent on serverX.xxxx.xxx . (ID 52 Details: The semaphore timeout period has expired (0x80070079))
More information
End time: 19/07/2014 03:11:06
Start time: 18/07/2014 22:00:00
Time elapsed: 05:11:05
Data transferred: 768 289,56 MB
Cluster node serverX.xxxx.xxx
Source details: G:\
Protection group members: 1
Details
Protection group: File Server Tape Protection
Library: Quantum PX500 Series Medium Changer
Tape Label (Barcode): File Server Tape Protection-00000230 (000043L4)
If I uninstall SCCM 2012 client, no more issue, backups succeed. I've asked our SCCM team, no specific task has been scheduled or deployed in SCCM.
I can't see anything abnormal in logs.
Any idea?

I have disabled "Configuration Manager Maintenance" and I have also tried to set the registry value HKLM\Software\Microsoft\CCM\CcmEval\NotifyOnly to TRUE and still the same issue.
I can't find any correlated errors in the Windows event logs, task scheduler history neither in the DPM logs.
I've increased the log level of DPM by following the following procedure
http://blogs.msdn.com/b/george_bethanis/archive/2013/11/04/how-to-collect-dpm-verbose-logs.aspx
Now i'm suspecting the maintenance job of Windows 2012 R2, i'll try to disabled this task. But the fact is that I don't have this backup issue if SCCM 2012 client is not installed.
I'm waiting for next logs and will keep you informed

Job SAP_COLLECTOR_FOR_PERFMONITOR in BI system

Hi gurus,
in my BI system netweaver 2004 'SAP_COLLECTOR_FOR_PERFMONITOR ' job runs successfully for every hour but when i check the job log shows as shown below. "Database system not supported" any help please.
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV
Clean_Plan:Cleaning up jobs of system BWU
Clean_Plan:finished
Database system not supported
Job finished
Regards
kumar

Hi All,
Sorry for late reply as I am on vacation and return back today only
I tried with above solutions but no use,
System details:
BI System SAP NetWeaver 2004s, Kernel -> 710
DB :Oracle 10g
OS : HP UNIX
This jobs runs for every one hour in our system each job log having different logs as shown below.
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                     on server bwsap1
Clean_Plan:Cleaning up jobs of system BW1
Clean_Plan:finished
Database system not supported
Job finished
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Database system not supported
Database system not supported
Job finished
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC
Database system not supported
Buffer statistics for bwsap1 transferred to MONI
Job finished
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                  on server bwsap1
Clean_Plan:Cleaning up jobs of system BW1
Clean_Plan:finished
Database system not supported
Reorganization of the database started
Reorganization of the database ended
Job finished
Job started
Step 001 started (program RSCOLL00, variant , user ID DDIC)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server bwsap1
Clean_Plan:Cleaning up jobs of system BW1
Clean_Plan:finished
Database system not supported
Buffer statistics for bwsap1 transferred to MONI
Job finished
Regards
Kumar

Collection_set_3_upload_upload job continously failing

I've SQL Server 2008 R2 SP2 CU5 (10.50.4276) on Windows 2008 R2. The collection_set_3_upload_upload job continously failing with below errors with retries, each retries takes minimum 40mins to few hours. Though the job is failing but still it
is uploading the data and i could see the data in the MDW graphs. But the job is failing. What could be the cause and what would the reason for failing? Below are the error message.
Message
Executed as user: ServiceAccount. Failed to log error for log id: 406725, generating message:
The thread "ExecMasterPackage" has timed out 3600 seconds after being signaled to stop.. Inner Error ------------------> Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "VServer\INS1"
Procedure: "sp_syscollector_event_onerror" Line#: 111 Error Number: 14684 Error State: 1 Error Severity: 16 Error Message: "Caught error#: 14262, Level: 16, State: 1, in Procedure: sp_syscollector_verify_event_log_id,
Line: 32, with Message: The specified @log_id ('406725') does not exist." Help File: "(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. The thread "ExecMasterPackage"
has timed out 3600 seconds after being signaled to stop. Unable to execute a stop collection event for log Id: 406725. Inner Error ------------------> Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance:
"VServer\INS1" Procedure: "sp_syscollector_verify_event_log_id" Line#: 32 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The specified @log_id ('406725') does not exist." Help File:
"(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Process Exit Code 259.
Executed as user: ServiceAccount. Failed to log error for log id: 406698, generating message: Failed to log package end event for package: "QueryActivityUpload". Inner Error ------------------> Row#: 0 Source:
"Microsoft SQL Server Native Client 10.0" Instance: "VServer\INS1" Procedure: "sp_syscollector_verify_event_log_id" Line#: 22 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The
specified @log_id ('406700') does not exist." Help File: "(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end.. Inner Error ------------------> Row#: 0
Source: "Microsoft SQL Server Native Client 10.0" Instance: "VServer\INS1" Procedure: "sp_syscollector_event_onerror" Line#: 111 Error Number: 14684 Error State: 1 Error Severity: 16 Error Message: "Caught
error#: 14262, Level: 16, State: 1, in Procedure: sp_syscollector_verify_event_log_id, Line: 32, with Message: The specified @log_id ('406698') does not exist." Help File: "(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}.
OLE DB Error Record dump end. Failed to log package end event for package: "QueryActivityUpload". Inner Error ------------------> Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "VServer\INS1"
Procedure: "sp_syscollector_verify_event_log_id" Line#: 22 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The specified @log_id ('406700') does not exist." Help File: "(null)",
Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end.Failed to log error for log id: 406698, generating message: Failed to log package end event for package: "Set_{2DC02BD6-E230-4C05-8516-4E8C0EF21F95}_Master_Package_Upload".
Inner Error ------------------> Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "VServer\INS1" Procedure: "sp_syscollector_verify_event_log_id" Line#: 22 Error Number: 14262
Error State: 1 Error Severity: 16 Error Message: "The specified @log_id ('406699') does not exist." Help File: "(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump
end.. Inner Error ------------------> Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "VServer\INS1" Procedure: "sp_syscollector_event_onerror" Line#: 111 Error Number: 14684
Error State: 1 Error Severity: 16 Error Message: "Caught error#: 14262, Level: 16, State: 1, in Procedure: sp_syscollector_verify_event_log_id, Line: 32, with Message: The specified @log_id ('406698') does not exist." Help File: "(null)",
Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Failed to log package end event for package: "Set_{2DC02BD6-E230-4C05-8516-4E8C0EF21F95}_Master_Package_Upload". Inner Error ------------------>
Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "VServer\INS1" Procedure: "sp_syscollector_verify_event_log_id" Line#: 22 Error Number: 14262 Error State: 1 Error Severity:
16 Error Message: "The specified @log_id ('406699') does not exist." Help File: "(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Failed to log error for
log id: 406698, generating message: The master package exited with error, previous error messages should explain the cause.. Inner Error ------------------> Row#: 0 Source: "Microsoft SQL Server Native Client 10.0" Instance:
"VServer\INS1" Procedure: "sp_syscollector_event_onerror" Line#: 111 Error Number: 14684 Error State: 1 Error Severity: 16 Error Message: "Caught error#: 14262, Level: 16, State: 1, in Procedure: sp_syscollector_verify_event_log_id,
Line: 32, with Message: The specified @log_id ('406698') does not exist." Help File: "(null)", Help context: 0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record d

Hi Jayakumar,
According to your description, collection_set_3_upload_upload job is failing. Based on my research, the issue could occur when the data is collected using an interim cache file, or the Data Collection set collects data every frequently.
To troubleshoot this issue, you could use these three solutions below.
1. Change the Server Activity collection to non-cached. This change would ensure that the data is uploaded as soon as it is collected without using an interim cache file.
2. Increase the collection frequency. The collection frequency is set to default of 15 seconds. This can be increased to 30 seconds or higher to prevent very large data being collected between the scheduled upload intervals.
3. Modify the sp_purge_data stored procedure for the purge job to run faster. An updated version of sp_purge_data is available
here. This will ensure that the purge job completes faster.
Regards,
Michelle Li

SM:EXEC SERVICES job getting failed in Solution manager

HI All,
SM:EXEC SERVICES job getting failed in solution mnager and job log will be fowlloing:
01-31-2012 19:09:21 Job started
01-31-2012 19:09:21 Step 001 started (program RDSMOPBACK_AUTOSESSIONS_ALL, variant , user ID BASISUSER)
01-31-2012 19:09:21 MemSize Begin = 796480 Bytes
01-31-2012 19:09:21 *******************************
01-31-2012 19:09:21 MemSize Begin = 1919120 Bytes
01-31-2012 19:09:23 Solution <000000106120000> "SID..." is being edited (Operations)
01-31-2012 19:09:23 <000000106120000> "SID..."(Operations)
01-31-2012 19:09:23 "Create_Periodic_Services" uses = 0 bytes
01-31-2012 19:09:23 "Create_Periodic_Services" uses = 690 us time
01-31-2012 19:09:23 Trying to perform session EC2000000001313
01-31-2012 19:09:24 MODEL_KEY: SID Installation Number: 6 MODEL_MODE: E MODEL_VERSNR 00001 MODEL_CLASS: EWA Data Model
01-31-2012 19:09:30 Definition nicht vorhanden
01-31-2012 19:09:33 Definition nicht vorhanden
01-31-2012 19:09:45 Internal session terminated with a runtime error (see ST22)
01-31-2012 19:09:45 Job cancelled
St22 Dump:
The exception 'CX_DSVAS_API_CONTEXT_INSTANCE' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program 'SAPLDSVAS_PROC' has to be
terminated.
Please suggest how to proceed further and provide your valuble inputs
Thanks
Nekkalapu

HI Siva,
I have done the changes according the note but still same problem.
Please suggest any other ways to resolve this issue .
Advance thanks
Regards
Nekkalapu

SM:SELFDIAGNOSIS background job getting failed in Solution manager

Hi All,
SM:SELFDIAGNOSIS background job getting failed in Solution manger server :
Job Log:
2-22-2012 16:44:02 Job started                                                                                00           516          S
2-22-2012 16:44:02 Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000000324, user ID BASISUSER)      00           550          S
2-22-2012 16:45:07 Internal session terminated with a runtime error (see ST22)                                     00           671          A
2-22-2012 16:45:07 Job cancelled                                                                                00           518          A
ST22: Dump:
Runtime Errors         ITAB_DUPLICATE_KEY
Date and Time          02-22-2012 16:45:07
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An entry was to be entered into the table
"\CLASS=CL_DSWP_SD_DIAGNOSE_CONSISTENT\METHOD=CHECK_USERS_BP\DATA=LT_USCP"
(which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ITAB_DUPLICATE_KEY" " "
"CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" or "CL_DSWP_SD_DIAGNOSE_CONSISTENTCM00M"
"CHECK_USERS_BP"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
KIndly Suggest to resolve the above issue
Thanks
Nekkalapu

HI,
Deatils:
SAP EHP 1 for SAP Solution Manager 7.0
SAP_ABA                701          0006    SAPKA70106
SAP_BASIS              701          0006    SAPKB70106
PI_BASIS               701          0006    SAPK-70106INPIBASI
ST-PI                  2008_1_700   0002    SAPKITLRD2
CRMUIF                 500          0004    SAPK-50004INCRMUIF
SAP_BW                 701          0006    SAPKW70106
SAP_AP                 700          0019    SAPKNA7019
BBPCRM                 500          0016    SAPKU50016
BI_CONT                704          0007    SAPK-70407INBICONT
CPRXRPM                400          0016    SAPK-40016INCPRXRP
ST                     400          0024    SAPKITL434
ST-A/PI                01M_CRM570   0000         -
ST-ICO                 150_700      0009    SAPK-15079INSTPL
ST-SER                 701_2010_1   0002    SAPKITLOS2
Thanks
Nekkalapu

Background job getting failed every day

Hi,
This background job getting failed every day.But this job was running fine initial periord.Please help me out this issue.
SAP_REORG_UPDATERECORDS
SAP_WP_CACHE_RELOAD_FULL
SLCA_LCK_SYNCHOWNERS
Regards
Naanas.

If this is R/3, then none of the above jobs should exist in the system, if scheduled by default with other standard jobs, then these should be removed
Note 1034532 - Changes for standard jobs
Note 931436 - SLCA_LCK_SYNCHOWNERS standard job terminates

Job SAP_COLLECTOR_FOR_PERFMONITOR failing in alternate hours

Similar Messages

Maybe you are looking for