Maintaince plan job was failed

Hi Team,
I have changed the backup path location local drive to other storage path. after that i have run the job but its failed below error:
Message
Executed as user: xxxxxx. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.2100.60 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  7:56:44 AM  Progress: 2014-09-22 07:56:44.78    
Source: {74CFAF94-FD09-4DB2-AED5-CCE166F673C7}      Executing query "DECLARE @Guid UNIQUEIDENTIFIER      EXECUTE msdb..sp...".: 100% complete  End Progress  Error: 2014-09-22 07:56:44.93    
Code: 0xC002F210     Source: Maintenance Cleanup Task Execute SQL Task     Description: Executing the query "EXECUTE master.dbo.xp_delete_file 0,N'\\xxxxxxx..." failed with the following error: "xp_delete_file()
returned error 2, 'The system cannot find the file specified.'". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.  End Error 
Warning: 2014-09-22 07:56:44.93     Code: 0x80019002     Source: Subplan_1      Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number
of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.  End Warning  DTExec: The package
execution returned DTSER_FAILURE (1).  Started:  7:56:44 AM  Finished: 7:56:45 AM  Elapsed:  0.829 seconds.  The package execution failed.  The step failed.
Request to you please suggest me on this.
subu

EXECUTE master.dbo.xp_delete_file 0,N'\\xxxxxxx..." failed with the following error: "xp_delete_file() returned error 2, 'The system cannot find the file specified.'".
Hello,
Seems you try to backup to a Network share? Make sure that SQL Server Service account do have permissions to access the share, incl write permissions.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Similar Messages

  • Maintanence plan jobs are failing

    Dear All,
    We are facing problems with maintenance plan jobs in SQL server 2012. All jobs are failing with Following error
    Executed as user: Testdbserver\SQLadmuser. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.3431.0 
    for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  2:35:25 PM  
    Could not load package "\Maintenance Plans\Db_Backup" because of error 0x80070005.  
    Description: Access is denied.  Source:   Started:  2:35:25 PM  Finished: 2:35:26 PM  Elapsed:  0.094 seconds.  
    The package could not be loaded.  The step failed.
    Server details are: windows 2008 server with sql server 2012 ENT with core based licence. And SQL server , agent services are running with user 'SQLadmuser' (Nonadmin windows user). SQLadmuser is
    having sysadmin server roleand in windows its nonadmin userid.
    SQL Server maintenance jobs are running under sql server agent service account(by default) but jobs are failing. So After that i have created
    credentials with proxy account and i have run those jobs with proxy account, all jobs are executing well with proxy.
    or If iam changing SQL server, agent service accounts from SQLadmuser  to
    local system the maintenance jobs are working perfect.
    I have cross verified all permissions and assigned SQLadmuser previlizes to the folders,root folders and regisries but still jobs are failing .
    Note: I have observed that some of SQL server related groups are not displaying in local groups and iam unable to find tose groups. one below are reflecting.
    1. Is there any relation with this sql groups to run the jobs?
    2. Why this jobs are not working with sql server agent service account?
    3. Does this create problems to whole SQL server instance in future?
    4. Running jobs with proxy account will be having any impact on server?
    Could you please help me to trouble shoot the maintenance jobs, Also sharing screenshots for reference.
    Thanks in advance,
    Nagesh
    Nagesh

    Hi Nagesh,
    For many of the maintenance plans which require access to file system you might have to give access for the SQL Server Agent account directly to those folders. Otherwise your SQL Agent wont have access to the file system. This is why your maintenance plan
    jobs like backups are failing.
    Now the best way of dealing with this issue is what you have done. Using proxy accounts. By using proxy accounts you are not giving any additional privileges to your SQL Agent account. There is no issue for using proxy accounts for SSIS packages or Maintenance
    plans where you need access outside of SQL. Infact proxy accounts are introduced for this purpose, so that Agent account can impersonate the credentials in the proxy and run the job in its security context.
    The reason why the jobs are successfull when you change your SQL Agent account to local system is that Local System account has access to the local file system.
    http://technet.microsoft.com/en-us/library/ms189064(v=sql.105).aspx
    HTH
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • Planning job: Processed with errors

    Hi,
    A planning job was run. In MC8I (Check Mass Processing), i see the following:
    Job:
    Variant:
    Info Structure:
    Version:
    Planning type:
    Created:
    Status: Processed with errors
    Although the status is Processed with errors, but the values transferred to PIR (MD63) seems alright. Can anyone shine light what is the problem?
    Thanks.

    Hi,
    Activities checked:      
       UEBERGABE    SOPDM_M  
    ---> whereby UEBERGABE is the Activity in MC8T; SOPDM_M is the Transfer profile in MC8S
    I had created another Info Structure, Planning Activity, Transfer Profile, Planning Type with the exact same configuration as per the earlier one. However, this error never happened. It was processed successfully. Therefore, I don't know where the problem is since the configurations seems exactly the same. One is processed successfully , the other is processed with errors.
    Thanks.

  • 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

  • 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

  • Easiest way to tell if a Job has failed

    Apologies if this is the wrong subject but I couldn't figure out which one covered my issue.
    We had a SQL Server failover to another server in the cluster. At the time, it was running a Job that has a single call to an SSIS package. That SSIS package calls a number of other packages and takes around 25 to 30 minutes to run all the way through.
    Because of that failover, the job was killed. There's no record in the Job log that it ran at all. I've always assumed that this is because the job is not actually logged until the first step finishes, whether it fails or not.
    Now, due to a problem in my design of this job, the fact it ran another morning before anyone came to me to ask for help, I've got a lot of tidying up to do. And to make the job more resilient.
    But that aside, is there any way to force it to log job starts so that the app support people will have a visual clue that all is not right when they view the Job Activity Monitor? Or do I have to code something myself around checking the SSIS logs I write?
    Nick Ryan SQL Server Developer OnePath (NZ) Ltd

    Thanks for sharing details with me!!
    Might be somewhere we may need some more clarity, so please let me say one more time what I tried to mention.
    I see point that I was trying to say is from your line:
    There was a suggestion I might be able to put some custom code in there that logs the start of the package. I'm not sure if that was suggesting I actually update the log that the Job Activity Monitor displays - that sounds a little dangerous but would be
    ideal if it could be done.
    As per my previous exe. when I was working for one of my client and they wanted to track each and every logging for everybody activities then they used to create such logging process by designing their own code and table structure and others and that worked
    for them as well. We just need to validate it properly. This can be implemented using so many better applicable dmvs to access multiple queries access and execution state.
    I Agree with you:
    "When the SQL Server fails over in the middle of the ETL job, obviously the email part is not going to work."
    However if you enable the Sql Server Agent Services restart option in job, then each service restart will also alert you and then you can map all these small small information from multiple sources and make sense about what might went wrong by putting these
    events logically into statements.
    I mean customized solutions are always for us apart from Sql Server Jobs execution logging support.
    Also If Team is not ready to cross the jobs monitor and check jobs log files then only process enforcement with proper benefits may help us.
    Thanks for allowing me to explain one more time.
    Santosh Singh

  • LMS 3.2 (solaris 10); RME 4.3.1 - ArchivePurge Job continuously failing

    currently there are 2134 devices in DCR; the customer originally had problems with UT reports and the error message "ogs_server_urn not found"; During troubleshooting I noticed that there were around 30000 instances in the job history; cleaning up the majority of these entries a problem with ArchivePurge job is left over:
    this job always ends with a status of "Failed" and no files are purged; Around 20 - 30 mins after its start time a /opt/CSCOpx/java_pidxxxx.hprof file is generated but the job will stay in running state for the next 27 hours ... Then it ends with little information in the job log.
    I attached some info which I collected during troubleshooting - and if necessary I also have trussed the PID at the very end before writing to the ResultSummary.obj until the process finishes.
    Also the job was deleted and readded. The information collected is from this new job.
    Does this point to a memory leak or is this just be a problem with the value for the ConfigJobManager.heapsize=512 in
    /opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/classes/JobManager.properties ??

    finally changing the heap size did not resolved the issue, but investigating this a little further showed why...
    the archive files for around 2100 devices where never purged in the past and due to restore of the databases over a few LMS releases (i.e. years) there where about over 1.2 million files...
    finaly with a wrapper script that purged the archive for the devices one by one for a specific time range the amount of files where dramatically reduced              /opt/CSCOpx/bin/cwcli config delete -u admin -l doing$host.log  -device $host -date 01/01/2000 01/01/2010
    to get a feeling of the work that must be done: ...the script ran for 12 days ... (good, that this installation is running on solaris)
    but now it is solved!

  • 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."

  • Very Urgent: Hyperion System 9 Planning license was encountered

    Hi,
    I am working on Planning Version 9.2X. On every weekend, Hyperion Planning and Essbase servers are scheduled to start. After that, all the services are being recycled as part of weekly maintenance. The next day, when I tried to login into Planning, I am experiencing below issue soon after the server restart. To overcome this, again I am stopping and starting all services. Please refer to the Below Error and its Server log.
    Can you please help in fixing this issue permanantly.
    And one more issue with other Planning Application: This application does not have this kind of problem, but it has strange issue. This application also goes under weekly maintenace and does not any problem with the login. But, If I won't login soon after the server and Services recycle, Business Rules that are scheduled to run won't start. I have to have login into Planning to make the Business Rules to run.
    Please suggest me if I need to change any settings with in the planning properties to overcome these issues.
    Thanks,
    UB.
    Planning Login issue errro and its log:
    A Problem with Hyperion System 9 Planning license was encountered. Please see log for details
    ####<Jan 24, 2010 10:31:56 AM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
    ####<Jan 24, 2010 10:35:29 AM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
    ####<Jan 24, 2010 6:51:56 PM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
    ####<Jan 24, 2010 6:55:26 PM EST> <Error> <HTTP> <Servername> <SharedServices> <ExecuteThread: '6' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-101215> <Malformed Request "/ HTTP 1.0". Request parsing failed, Code: -10>
    #

    user640496 wrote:
    Why have to login after services recycled? Is it a product bug or it is common practice to login into the Planning to run the BR's once the services recycled.It has always been that way, I have never understood the logic but that is the way it is...
    Also, Please give your inputs on this issue which was raised in the begining of this thread.
    A Problem with Hyperion System 9 Planning license was encountered. Please see log for details
    I am not sure on that one, have you checked any of the license server logs, I would contact Oracle if nobody else comes up with some ideas.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Job is failing with the following error- Error calling a method of the tree

    dear SDNers,
    my question is where do i need to look for error.
    Will this be an ABAP issue?
    Please guide
    DETAILS
    In SM37 when we see the job XYZ, we get the following details.
       Job                              Ln    Job CreatedB    Status          Start date     Start time      Duration(sec.)     Delay (sec.)
      XYZ                                                                    Canceled        16.11.2009    10:11:30                  9                         27
    When the job log is checked this , we get the below details.
    The job XYZ is failing with the following error.
    Date      Time     Class  No.   Message
    +----
    +----
    2009/11/16 05:03:01 | 00     516 | Job started
    2009/11/16 05:03:01 | 00     550 | Step 001 started (program RBDMON00, variant
    SBCI287, user ID ABCDEF)
    2009/11/16 05:03:03 | TREE_C 000 | Error calling a method of the tree control
    2009/11/16 05:03:03 | 00     518 | Job cancelled
    Equest your assistance in knowing where to find the error for this.
    I have no clue as to where and how i need to debug or where i should i be looking for error.
    In BD87, the selection screen paramters that are given are changed on date (from and to) and IDOC status 51,66,69 and 64 and the message type is "Öutbound interface of picked shipments"
    Please guide.
    Regards,
    SuryaD.
    Edited by: SuryaD on Nov 23, 2009 5:36 PM
    Edited by: SuryaD on Nov 23, 2009 11:14 PM

    > 1. There is a job name ABCDEF
    > 2. When this job is run then the status shows cancelled and the job error log shows tHe details that "error calling a method of the tree control"
    > 3.ThIs error also points fingers to /link to BD87 as seen in the job log " (program RBDMON00, variant \SBCI287, user ID KRISF)"
    >
    BD87 is an IDOC processing.
    > My question to you Sampath.
    >
    > in order to answer your question on whether it is ALv or SALV.. please tell me as to how will i know which progrm is associated with the job ABCDEF?
    >
    Go to sm37 - double click on the job that was failed - Click on Step (on application tool bar) to get the program name - double click on the program name - new popup will be opened - then copy the program and variant
    Go to se38 - enter the program - execute (F8) - choose the variant that is there in the background job - run in forground first
    if the run is good - then check the program - SE38 - Display the program then see
    I just saw the above message BD87... .if that is true, you dont have to do all these
    I dont think it is possible to schedule a job with BD87. Is this the first time or is any job completed without errors for this?

  • V3 Collector Jobs are failing

    Hi All,
    We have newly insatlled Purchasing LIS (02) dataflow. We have enhanced 2LIS_02_ITM datasource. We are able to fill the setup tables and perform the INIT load.
    But the V3 extractor job is failing. The ABAP dump says - SY-SUBRC = 2. Changes made to structures..
    Please let me know your views.
    Regards and Thamks,
    Vivek Das Gupta

    Hi,
    Is there is another system with the same client and if the data source if you have already done some activity on that client.
    the error could be because you did the changes to data source when there was some delta records present for that data source.
    try delete the existing delta queue and the any entries from LBWQ for this data source and and from all the clients if there are any.
    then do a reinit and start the delta again.
    hope it helps.
    Ajeet

  • Some jobs are failing due to listener.

    Hi all,
    Only some jobs are failing ,and remaining jobs succeeded.I checked the listener, it was up only.(10.2.0.2 on linux)
    the reason for failing jobs showed is
    ORA-12541: TNS:no listener
    Can you please tell what is the reason for this
    Thanks in advance,
    Prashant

    Some of the failing jobs could be referencing a db link and you need to verify the tns alias being used in the database links
    Use tnsping <tnsalias> to verify the connect string

Maybe you are looking for

  • N9 - Download error on ovi store

    I tried to download some software (File Manager Beta and Battery Usage) but failed. Ovi store showed "Can't install" "Unable to continue installation due to unresolved error".  I tried both WLAN and 3G but it failed in both way. How can I install app

  • Transitioning to iCloud

    I am not sure where to save my information before I convert from MobileMe to iCloud.  Can it be saved on my iMac under documents or does it need to be transferred to a separate disc?

  • My Side Navigation menu and spry tabbed panels aren't working together. Can I fix this?

    I have made some tabbed panels, but my side navigation is not working correctly now. See the following page for an example. http://www.foxthermalinstruments.com/products/index.php   When you mouse (hover) over "Applications" on the side navigation me

  • CC 2014 crashing after importing a project

    converted a project from last years CC to the new 2014 and it keeps crashing????

  • Opening Accordion Panels w/ MouseOver

    I would like to customize an accordion widget so the panel contents open when I move my mouse over the panel tab. The default setting opens only with mouse click. How can I change this? Is it possible to add Dreamweaver behaviors to Spry widgets, or