Sporadic problem: The report server has encountered a configuration error. Logon failed for the unattended execution account.

I have 2 reports that have subscriptions.   I am sporadically getting this error.   If it was really a configuration problem then I think I should get the error every time.     Does any one have any suggestions of
what to look for?    I have not found any errors relating to this problem in the server logs.

Hi ClareD,
According to the error message, there is an unattended execution account specified on the report server. Based on my research, the issue always occurs when you are using incorrect login name and password. Such as the password expired. Please make sure you
set the correct login name and password.
Besides, please double check if the user has the following permission on the reporting service database server:
Public and RSExecRole roles for the  ReportServer database.
RSExecRole role for the master, msdb, and ReportServerTempDB databases.
If he does not have the permission, please try to grant the proper permission first. For more information, please refer to the article:
http://technet.microsoft.com/en-us/library/ms159133.aspx
If there are any other questions, please feel free to ask.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Similar Messages

  • The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) Log on failed. Ensure the user name and password are correct. (rsLogonFailed) Logon failure: unknown user name or bad

    The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError)
    Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
    Logon failure: unknown user name or bad password 
    am using Windows integrated security,version of my sql server 2008R2
    I have go throgh the different articuls, they have given different answers,
    So any one give me the  exact soluction for this problem,
    Using service account then i will get the soluction or what?
    pls help me out it is urgent based.
    Regards
    Thanks!

    Hi Ychinnari,
    I have tested on my local environment and can reproduce the issue, as
    Vaishu00547 mentioned that the issue can be caused by the Execution Account you have configured in the Reporting Services Configuration Manager is not correct, Please update the Username and Password and restart the reporting services.
    Please also find more details information about when to use the execution account, if possible,please also not specify this account:
    This account is used under special circumstances when other sources of credentials are not available:
    When the report server connects to a data source that does not require credentials. Examples of data sources that might not require credentials include XML documents and some client-side database applications.
    When the report server connects to another server to retrieve external image files or other resources that are referenced in a report.
    Execution Account (SSRS Native Mode)
    If you still have any problem, please feel free to ask.
    Regards
    Vicky Liu
    Vicky Liu
    TechNet Community Support

  • The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) Log on failed. Ensure the user name and password are correct. (rsLogonFailed) The user name or password is incorrect

    I am able to run the report fine in BIDS in the preview window, and it deployes fine.  When it goes to view the report in the browser, I get the following error.  There is no domain, I am using a standalone computer with SQL Server and SSRS on
    this one machine.
    Can anyone point to where I might configure the permission it is looking for?  thanks!  Steven
    The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError)
    Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
    The user name or password is incorrect
    Steven DeSalvo

    Hi StevenDE2012,
    Based on the error message "The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError)", it seems that the Unattended Execution Account settings in Reporting Services
    Configuration is not correct.
    Reporting Services provides a special account that is used for unattended report processing and for sending connection requests across the network. Unattended report processing refers to any report execution process that is triggered by an event rather than
    a user request. The report server uses the unattended report processing account to log on to the computer that hosts the external data source. This account is necessary because the credentials of the Report Server service account are never used to connect
    to other computers. To configure the account, please refer to the following steps:
    Start the Reporting Services Configuration tool and connect to the report server instance you want to configure.
    On the Execution Account page, select Specify an execution account.
    Type the account and password, retype the password, and then click Apply.
    In addition, please verify you have access to the Report Server database by following steps:
    Go to SQL Server Reporting Services Configuration Manager, make sure the configuration is correct.
    Go to Database, Verify that you can connect to the database.
    Make sure you are granted public and RSExecRole roles.
    Reference:
    Configure the Unattended Execution Account
    Configure a Report Server Database Connection
    If the problem is unresolved, i would appreciate it if you could give us detailed error log, it will help us move more quickly toward a solution.
    Thanks,
    Wendy Fu

  • The report server has encountered a configuration error. (rsServerConfigurationError)

    Hi,
        One of the server in my organization running SQL server 2008 reporting services.
    Users are complaining that they are not able to fetch reports, after going through logs its been found that following three errors are coming although reporting services are running & both report DBs are online :-
    Report Server (MSSQLSERVER) cannot load the Windows extension.
    Report Server (MSSQLSERVER) cannot connect to the report server database.
    Report Server Windows Service (MSSQLSERVER) has not been granted access to the catalog content.
    Following is the error when we click on reporting link :-
    The report server has encountered a configuration error. (rsServerConfigurationError)
    We tried restarting Reporting services but still its not working, reporting services & DBs are on same machine.
    Same server was rebooted 4 days ago.
    Can anyone please help here.

    Hi Abhishek,
    According to the error message, it seems that the issue is caused by the account used to connect catalog database does not have permissions to access the catalog content.
    To fix this issue, please refer to the following steps:
    Open Reporting Services Configuration Manager.
    Go to "Encryption Keys" to backup the Encryption Key.
    Go to "Database" tab to click "Change Credentials" to reset the connections.
    If everything is configured correctly but still it didn't work, try to delete encrypted content. Please note that once we delete encrypted content, we cannot recover it. We must re-specify connection strings and stored credentials, and we must activate subscriptions.
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Report Server has encountered a SharePoint error.

    Hi,
    I am getting following error when i try to browse the reporting service url.
    http://servername/ReportServer
    Report Server has encountered a SharePoint error. The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
    It is configured in sharepoint integrated mode.
    Created a site collection with "Business Intelligence Center" and published couple of reports and it gets renderd. Everything seems to be working except for browsing the reporting service URL.  Here is the Log info.
    ******************** Start LOG Info ********************************************************
    library!ReportServer_0-7!2b14!06/26/2012-03:26:56:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: , Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint
    error. ---> System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
       at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale,
    String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrThemedCssFolderUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String&
    pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags, Boolean& pbOverwriteMUICultures, Boolean& pbMUIEnabled,
    String& pbstrAlternateMUICultures, Int32& puiVersion, Int16& pnClientTag)
       at Microsoft.SharePoint.Library.SPRequest.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale, String&
    pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrThemedCssFolderUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl,
    String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags, Boolean& pbOverwriteMUICultures, Boolean& pbMUIEnabled, String& pbstrAlternateMUICultures,
    Int32& puiVersion, Int16& pnClientTag)
       at Microsoft.SharePoint.SPWeb.InitWebPublic()
       at Microsoft.SharePoint.SPWeb.get_ID()
       at Microsoft.ReportingServices.SharePoint.Objects.RSSPImpWeb.get_ID()
       at Microsoft.ReportingServices.SharePoint.Utilities.CatalogItemUtilities.CreateCatalogItem(RSSPWeb web)
       at Microsoft.ReportingServices.SharePoint.Server.SharePointDBInterface.InternalFindObjects(ExternalItemPath wssUrl, CatalogItemList& children)
       at Microsoft.ReportingServices.SharePoint.Server.SharePointDBInterface.FindObjectsNonRecursive(ExternalItemPath wssUrl, CatalogItemList& childList, Security secMgr, IPathTranslator pathTranslator, Boolean appendMyReports)
       --- End of inner exception stack trace ---;
    webserver!ReportServer_0-7!2b14!06/26/2012-03:26:56:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> System.IO.DirectoryNotFoundException:
    The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
    *****************************  END LOG info  ***************************************
    Any help is greatly appreciated.
    Thanks and Regards,
    Manjunath

    Detach the contentdb from SP and then reattach it. To do that you'd run this command:
    STSADM -o deletecontentdb -url https://******.com -databasename whateverdb
    Then to add it back you'd do:
    STSADM -o addcontentdb url https://******.com -databasename whateverdb
    Thank you Mike Yin, I have confirmed that this solution works, I had the exact issue, my investigation steps are in this order:
    1. Verify if there is a orphaned site  (use stsadm.exe -o enumsites or stsadm -o enumallwebs or Test-SPContentDatabase
    2. On my case I found the site orphaned on the root url [/] so I cannot just do a stsadm -o deletesite -force -siteid, so I did is to Remove Content from the CA and then re-add the content db back using CA. (Application Management > open the affected
    Content DB and click the Remove content database checkbox. Then click Add a content Database, and re-add the same contentDB.
    3. Verify in the RS Config Manager and click the RS Web Service URL, to see if works.

  • The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

    got event ID 4015 and source DNS-Server-Service. please suggest how to fix this issue
    The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
    Raj

    Hi
     first run "ipconfig /flushdns" and then "ipconfig /registerdns" finally restart dns service and check the situation,also you can check dns logs computer management ->Event viewer->Custom Views->Server roles->DNS.

  • Logon failed for the unattended execution account.

    Hi while am running my report it is throwing the below error.I have verified entire config file,
    And i have recently uninstall and install the Reporting services after installing this i have faced this error ,shell i need to remove any old files from the configmgr or what why it is not working.The follwg error  i have get while am running the report
    The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError)
    Log on failed. Ensure the user name and password are correct. (rsLogonFailed)
    Logon failure: unknown user name or bad password
    It will create any logfiles and entries  in the logfile Folder and There is no folder for rsConfig in the Root Folder,
    was it made any thing wrong or what give me the soluction
    Please give me the right soluction for this problem.

    Hi Ychinnari,
    According to your description, you comes across an error when you run a report.
    In your scenario, the issue could cause by the Execution Account you have configured in the Reporting Services Configuration Manager is not correct. Please go to Reporting Services Configuration Manager and connect to the report server instance, then open
    the Execution Account page, update the username and password for the execution account, finally, restart the Reporting Services for this instance.
    Since you mentioned you can’t find the log files, please check the server which has reporting server instance installed with this path: C:\Program Files\Microsoft SQL Server\<instance name>\Reporting Services\LogFiles to check the error log.
    If you have any question, please feel free to ask.
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support

  • Getting an error prompt "the facebook server has returned an unknown error and is not able to fulfill your request. (2001)"

    Hi. I need help regarding facebook for blackberry. I cannot post any status update, i keep on receiving an error prompt "the facebook server has returned an unknown error and is not able to fulfill your request. (2001)".  it has been like this for the past 3 days. I already did the hard reboot many times, re-send service book though i do'nt think it's needed, and tried uninstalling and reinstalling the facebook application too but still getting the same error everytime i try to post a status update. I can comment to messages on my wall and other profiles, the news feed is updating in time too, i can also log-in and out to facebook with no problem, as well as other applications on my phone like foursquare, BBm, ubersocial, BB protect, BB app world, etc, are all working perfectly fine. And now I don't know what seems to be the problem.
    I've already contacted my network provider and told me that the error i'm getting is beyond their scope.
    Is anybody having the same problem as mine? 
    Can someone in BB support team help me regarding this issue and tell me what should I do?
    Thank you in advance. 

    I got the same issue !! Since I've updated my Facebook app 2 or 3 week ago !
    I can not  update my status and check-in ! It gives me "the facebook server has returned an unknown error and is not able to fulfill your request. (2001) "
    I can upload photo, put comment on people, like people status/picture. The news feed update perfectly !
    I also  tryied to uninstall reinstall the app, reboot etc etc ! I still can't update my status !!!! I've installed 3.0.0.17 this morning and the issue is still there...
    I've remarked one thing... On my facebook under "privacy setting/the Apps, Games and Websites" I used to have a "blackberry app" installed. It's not there anymore and I didn't remove it.
    I don't know how to reinstall it...

  • The parsing engine has encountered a fatal error condition......

    I am creating a new Entitilement Segment. When I sync, I get a parsing
    exception. The error stack is described below. The same error message
    is displayed while starting the server.
    Any help is appreciated.
    Kumar
    URI : /contentselectors/GlobalContentSelectors.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Resource key "Corrective Action" not found for class
    com.bea.commerce.tools.server.SynchronizationProgress. null
    ==================================================================
    URI : /entitlements/GlobalEntitlements.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Resource key "Corrective Action" not found for class
    com.bea.commerce.tools.server.SynchronizationProgress. null
    ==================================================================
    URI : /segments/GlobalClassifications.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.reposit

    Hi kumar,
    did you find what was the resolution for this.
    thanks

  • Parts Requirement Create Order Error:Validation Failed for the field - Shipping Method DHL

    Trying to create Parts Requirement.
    Error message on clicking "Create Order" button: "Validation Failed for the field - Shipping Method DHL"
    Please suggest the Setup that needs to be done for this.

    Kinck
    The same script worked for me in vision (R12.1). You may have issues with your defaulting of a number of attributes that you are not passing in the API (like price list, line type and so on). You may want to check them.
    Thanks
    Nagamohan

  • Error: Validation failed for the field - Status While creating Sales Order

    Hi,
    I am getting an error while trying to create sales order header.
    I have tried using provided in the metalink as well but it still doesn't seem to work.
    I am on R12.1.1
    Can somebody help me out on this?
    The code is
    set serveroutput on
    DECLARE
    l_header_rec OE_ORDER_PUB.Header_Rec_Type;
    l_header_rec1 OE_ORDER_PUB.Header_Rec_Type;
    l_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
    l_line_tbl1 OE_ORDER_PUB.Line_Tbl_Type;
    l_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type;
    l_header_adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
    l_line_adj_tbl OE_ORDER_PUB.line_adj_tbl_Type;
    l_header_scr_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
    l_line_scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
    l_request_rec OE_ORDER_PUB.Request_Rec_Type ;
    l_return_status VARCHAR2(1000);
    l_msg_count NUMBER;
    l_msg_data VARCHAR2(1000);
    p_api_version_number NUMBER :=1.0;
    p_init_msg_list VARCHAR2(10) := FND_API.G_FALSE;
    p_return_values VARCHAR2(10) := FND_API.G_FALSE;
    p_action_commit VARCHAR2(10) := FND_API.G_FALSE;
    x_return_status VARCHAR2(1);
    x_msg_count NUMBER;
    x_msg_data VARCHAR2(100);
    p_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC; 
    p_old_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC;
    p_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
    p_old_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
    p_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
    p_old_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
    p_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
    p_old_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
    p_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
    p_old_Header_Price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
    p_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
    p_old_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
    p_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
    p_old_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
    p_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
    p_old_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
    p_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
    p_old_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
    p_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
    p_old_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
    p_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
    p_old_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
    p_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
    p_old_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
    p_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
    p_old_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
    p_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
    p_old_Line_Price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
    p_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
    p_old_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
    p_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
    p_old_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
    p_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
    p_old_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
    p_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
    p_old_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
    p_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
    p_old_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
    p_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
    p_old_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
    p_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type := OE_ORDER_PUB.G_MISS_REQUEST_TBL;
    x_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type;
    x_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
    x_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
    x_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
    x_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
    x_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
    x_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
    x_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type; 
    x_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
    x_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
    x_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
    x_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
    x_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
    x_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
    x_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
    x_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
    x_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type;
    x_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
    x_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type; 
    X_DEBUG_FILE VARCHAR2(100);
    l_line_tbl_index NUMBER;
    l_msg_index_out NUMBER(10);
    BEGIN
    oe_debug_pub.debug_on;
    DBMS_APPLICATION_INFO.set_client_info (121);
    dbms_output.enable(1000000);
    fnd_global.apps_initialize(2787,50703,660); -- pass in user_id, responsibility_id, and application_id
    oe_msg_pub.initialize;
    oe_debug_pub.initialize;
    MO_GLOBAL.init('ONT');
    X_DEBUG_FILE := OE_DEBUG_PUB.Set_Debug_Mode('FILE');
    oe_debug_pub.SetDebugLevel(5); -- Use 5 for the most debuging output, I warn you its a lot of data
    dbms_output.put_line('START OF NEW DEBUG');
    --This is to CREATE an order header and an order line
    --Create Header record
    --Initialize header record to missing
    l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
    l_header_rec.pricing_date := SYSDATE;
    l_header_rec.sold_to_org_id := 2096;
    l_header_rec.ordered_date := SYSDATE;
    l_header_rec.sold_from_org_id := 121     ;
    l_header_rec.salesrep_id := -3;
    l_header_rec.order_type_id := 1003;
    l_header_rec.operation := OE_GLOBALS.G_OPR_CREATE;
    l_line_tbl_index :=1;
    -- FIRST LINE RECORD
    -- Initialize record to missing
    l_line_tbl(l_line_tbl_index) := OE_ORDER_PUB.G_MISS_LINE_REC;
    -- Line attributes
    l_line_tbl(l_line_tbl_index).inventory_item_id := 124516;
    l_line_tbl(l_line_tbl_index).ordered_quantity := 500;
    l_line_tbl(l_line_tbl_index).ship_from_org_id := 563;
    l_line_tbl(l_line_tbl_index).operation := OE_GLOBALS.G_OPR_CREATE;
    -- CALL TO PROCESS ORDER Check the return status and then commit.
    OE_ORDER_PUB.process_order (
      p_api_version_number => 1.0
      , p_init_msg_list => fnd_api.g_false
      , p_return_values => fnd_api.g_false
      , p_action_commit => fnd_api.g_false
      , x_return_status => l_return_status
      , x_msg_count => l_msg_count
      , x_msg_data => l_msg_data
      , p_header_rec => l_header_rec
      , p_line_tbl => l_line_tbl
      , p_action_request_tbl => l_action_request_tbl
       -- OUT PARAMETERS
      , x_header_rec => l_header_rec1
      , x_header_val_rec => x_header_val_rec
      , x_Header_Adj_tbl => x_Header_Adj_tbl
      , x_Header_Adj_val_tbl => x_Header_Adj_val_tbl
      , x_Header_price_Att_tbl => x_Header_price_Att_tbl
      , x_Header_Adj_Att_tbl => x_Header_Adj_Att_tbl
      , x_Header_Adj_Assoc_tbl => x_Header_Adj_Assoc_tbl
      , x_Header_Scredit_tbl => x_Header_Scredit_tbl
      , x_Header_Scredit_val_tbl => x_Header_Scredit_val_tbl
      , x_line_tbl => l_line_tbl1
      , x_line_val_tbl => x_line_val_tbl
      , x_Line_Adj_tbl => x_Line_Adj_tbl
      , x_Line_Adj_val_tbl => x_Line_Adj_val_tbl
      , x_Line_price_Att_tbl => x_Line_price_Att_tbl
      , x_Line_Adj_Att_tbl => x_Line_Adj_Att_tbl
      , x_Line_Adj_Assoc_tbl => x_Line_Adj_Assoc_tbl
      , x_Line_Scredit_tbl => x_Line_Scredit_tbl
      , x_Line_Scredit_val_tbl => x_Line_Scredit_val_tbl
      , x_Lot_Serial_tbl => x_Lot_Serial_tbl
      , x_Lot_Serial_val_tbl => x_Lot_Serial_val_tbl
      , x_action_request_tbl => l_action_request_tbl
      dbms_output.put_line('OM Debug file: ' ||oe_debug_pub.G_DIR||'/'||oe_debug_pub.G_FILE); 
      oe_debug_pub.debug_off;
      -- Retrieve messages
      FOR i IN 1 .. l_msg_count
      LOOP
       Oe_Msg_Pub.get( p_msg_index => i
        , p_encoded => Fnd_Api.G_FALSE
        , p_data => l_msg_data
        , p_msg_index_out => l_msg_index_out);
       DBMS_OUTPUT.PUT_LINE('message is: ' || l_msg_data);
       DBMS_OUTPUT.PUT_LINE('message index is: ' || l_msg_index_out);
      END LOOP;
    -- Check the return status
    IF l_return_status = FND_API.G_RET_STS_SUCCESS
    THEN
      dbms_output.put_line('Process Order Sucess');
      dbms_output.put_line('new Header id:' || l_header_rec1.header_id);
    ELSE
      dbms_output.put_line('Failed');
    END IF;
    Commit;
    END; Regards
    knick

    Kinck
    The same script worked for me in vision (R12.1). You may have issues with your defaulting of a number of attributes that you are not passing in the API (like price list, line type and so on). You may want to check them.
    Thanks
    Nagamohan

  • An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help The profile for the user is a temporary profile. (Exception from HRESULT: 0x80090024)

    An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help The profile for the user is a temporary profile. (Exception from HRESULT: 0x80090024) 
     while proview the report i will get this error am using sql server 2008R2,
    can u plesae hlep me out for this
     

    <Header>
      <Product>Microsoft SQL Server Reporting Services Version 2009.0100.1600.01 ((KJ_RTM).100402-1539 )</Product>
      <Locale>English (United States)</Locale>
      <TimeZone>W. Europe Standard Time</TimeZone>
      <Path>C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\Logfiles\ReportServerService__01_30_2015_03_09_32.log</Path>
      <SystemName>WEGDACM1</SystemName>
      <OSName>Microsoft Windows NT 6.1.7601 Service Pack 1</OSName>
      <OSVersion>6.1.7601</OSVersion>
      <ProcessID>4880</ProcessID>
      <Virtualization>Hypervisor</Virtualization>
    </Header>
    rshost!rshost!5e4!01/30/2015-03:09:32:: i INFO: Currently registered url http://+:80/ReportServer_MSSQLSERVEREPORT/ on endpoint 2
    rshost!rshost!5e4!01/30/2015-03:09:32:: e ERROR: Failed to register url=http://+:80/Reports/ for endpoint 3, error=b7.
    rshost!rshost!5e4!01/30/2015-03:09:32:: w WARN: Endpoint 3 is enabled but no url is registered for vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportManager.
    servicecontroller!DefaultDomain!1e30!01/30/2015-03:09:32:: e ERROR: Error creating HTTP endpoint. System.Runtime.InteropServices.COMException (0x800700B7): Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7)
       at Microsoft.ReportingServices.HostingInterfaces.IRsUnmanagedCallback.CreateHttpEndpoint(RsAppDomainType application, String[] urlPrefixes, Int32 cPrefixes, String[] hosts, Int32 cHosts, Boolean wildCardPresent, String virtualDirectory, String
    filePath, Int32 authType, Int32 logonMethod, String authDomain, String authRealm, Boolean authPersist, Int32 extendedProtectionLevel, Int32 extendedProtectionScenario, Boolean enabled)
       at Microsoft.ReportingServices.Library.ServiceAppDomainController.SetWebConfiguration(RunningApplication rsApplication, Boolean enabled, String folder)
    rshost!rshost!65c!01/30/2015-03:09:32:: i INFO: Endpoint 4 is disabled and no url is registered vdir=/ReportServer_MSSQLSERVEREPORT/ReportBuilder, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportServer\ReportBuilder.
    rshost!rshost!1e30!01/30/2015-03:09:32:: i INFO: Derived memory configuration based on physical memory as 16776696 KB
    servicecontroller!DefaultDomain!1e30!01/30/2015-03:09:32:: i INFO: Recycling the service from the default domain
    rshost!rshost!1e30!01/30/2015-03:09:46:: i INFO: Application domain type WindowsService statistics: created: 7, unloaded: 7, failed: 0, timed out: 0.
    appdomainmanager!DefaultDomain!1e30!01/30/2015-03:09:46:: i INFO: Appdomain:11 WindowsService_7 started.
    library!WindowsService_7!1e30!01/30/2015-03:09:46:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    servicecontroller!WindowsService_7!1e30!01/30/2015-03:09:46:: e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
    error. 
    resourceutilities!WindowsService_7!1e30!01/30/2015-03:09:47:: i INFO: Reporting Services starting SKU: Enterprise
    servicecontroller!WindowsService_6!1e30!01/30/2015-03:09:47:: i INFO: Service controller exiting.
    appdomainmanager!DefaultDomain!1e30!01/30/2015-03:09:47:: i INFO: Appdomain:10 unregistered.
    appdomainmanager!DefaultDomain!1e30!01/30/2015-03:09:47:: i INFO: Appdomain:10 WindowsService_6 unloading.
    appdomainmanager!DefaultDomain!1f40!01/30/2015-03:09:47:: i INFO: AppDomain:10 0 pending unload(s)
    library!WindowsService_7!2410!01/30/2015-03:09:47:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    library!WindowsService_7!2410!01/30/2015-03:09:47:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
    error. 
    library!WindowsService_7!2410!01/30/2015-03:09:47:: e ERROR: ServiceStartThread: Attempting to start service again...
    library!DefaultDomain!202c!01/30/2015-08:04:43:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    library!DefaultDomain!202c!01/30/2015-08:25:26:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    library!DefaultDomain!202c!01/30/2015-08:26:16:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    The above is my log file pls find it resolve my problem,am trying to add the encryption key to my configuration seetings it will through the error like The profile you were used is temporary profile.

  • SQL Server reporting server 2005 having error. 'The report server is not responding. Verify that report server is running and can be accessed from this computer'

    Hi team,
    I got below error message in SQL Server 2005 reporting service.
    ''The report server is not responding. Verify that report server is running and can be accessed from this computer'
    also in reports, i am getting below error:
    "The encrypted value for the "LogonCred" configuration setting cannot be decrypted. (rsFailedToDecryptConfigInformation)
    Get Online Help
    The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
    Get Online Help "
    Please find below log:
    <Header>
      <Product>Microsoft SQL Server Reporting Services Version 9.00.4060.00</Product>
      <Locale>en-US</Locale>
      <TimeZone>Eastern Daylight Time</TimeZone>
      <Path>F:\Program Files\Microsoft SQL Server\MSSQL.6\Reporting Services\LogFiles\ReportServer__07_28_2014_09_08_41.log</Path>
      <SystemName>MFLDDDBS04</SystemName>
      <OSName>Microsoft Windows NT 5.2.3790 Service Pack 2</OSName>
      <OSVersion>5.2.3790.131072</OSVersion>
    </Header>
    w3wp!webserver!1!7/28/2014-09:08:41:: i INFO: Reporting Web Server started
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing ConnectionType to '1'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsSchedulingService to 'True'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsNotificationService to 'True'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsEventService to 'True'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsWebServiceEnabled to 'True'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing ProcessRecycleOptions to '0'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonFlags to '1064'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException'  as specified in Configuration
    file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing SecureConnectionLevel to '0'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DisplayErrorLink to 'True'  as specified in Configuration file.
    w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WebServiceUseFileShareStorage to 'False'  as specified in Configuration file.
    w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Reporting Services starting SKU: Enterprise
    w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Evaluation copy: 0 days left
    w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information., CryptUnprotectData:
    Win32 error:13;
     Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
    w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted., ;
     Info: Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. See the report server log files for more information.
       at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.UnprotectData(Byte[] data, Int32 dwFlags, Boolean transitoryData)
       at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectData(String data, Boolean transitoryData)
       at Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(String encryptedData, String element)
       --- End of inner exception stack trace ---

    Hi Vivek,
    In Reporting Services, values for LogonUser, LogonDomain, and LogonCred are created when the report server connection is configured to use a domain account. As to the error that “The encrypted value for the "LogonCred" configuration setting cannot be decrypted”,
    we can know that it relates to the domain account for report server connection.
    To fix this issue, we can refer to the following steps:
    Log in to SQL Server Database Engine in SQL Server Management Studio.
    Under Security folder, give sufficient permissions for your domain account.
    Open your Reporting Services Configuration (go to Start -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporting Services Configuration)
    Navigate to the Database Setup tab, select ‘Service Credentials’ as the Credentials Type, then type your domain account and password in there. Press Apply.
    Restart the Report Server services.
    Reference:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2d05b404-83aa-4fb2-bba6-52b587e890ec/sql-2005-rs-configuration-tool-encryption-key-error
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • [Forum FAQ] The Reporting Server cannot be reinstalled on a same SQL Server Reporting Service instance

    Symptom: Sometimes, when you want to reinstall the Reporting Server Role for Operation Manager 2012,
    but you may encounter an issue that the Reporting Server Role cannot be reinstalled after you successfully uninstall it. When you check the System Center Operation Manager installation log, you can find the following error as shown in Figure 1.
    Figure 1: Reporting Server Role cannot be reinstalled
    It seems that the SQL Server Reporting Service has not been configured properly. When you open Reporting Services Configuration Manager to check the settings, the settings seem fine though.
    Even you recreate Reporting Service Database, the error remains.
    After reviewing the OpsMgrSetupWizard.log, we get the following errors when wizard try to connect to SQL Server Reporting Instance (Figure 2).
    [07:24:05]:    Error:  :CheckHttpAddressResponse failed: Threw Exception.Type: System.Net.WebException, Exception Error Code: 0x80131509, Exception.Message:
    The remote server returned an error: (500) Internal Server Error.
    [07:24:05]:    Error:  :StackTrace:   at System.Net.HttpWebRequest.GetResponse() at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckHttpResponseFromSRSUrl(String
    httpSite)
    Figure 2: Error Log -1
    It indicates the Reporting Service encounters an internal error. The Website cannot handle the request. So you may check the Reporting Service log which is located in C:\Users\Administrator.SCOM2012\AppData\Local\SCOM\LOGS
    and the following errors may be found (Figure 3).
    library!ReportServer_0-18!1448!03/30/2014-02:53:23:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    Unable to load assembly Microsoft.EnterpriseManagement.Reporting.Security, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.  ---> System.IO.FileNotFoundException:
    Could not load file or assembly 'Microsoft.EnterpriseManagement.Reporting.Security' or one of its dependencies. The system cannot find the file specified.
    File name: 'Microsoft.EnterpriseManagement.Reporting.Security'
    Figure 3: Error Log -2
    Reason: After the Reporting Server is installed on a SSRS instance, the Reporting Server of SCOM
    needs to modify the web.config and rsreportserver.config  file to add its own assembly to make the Reporting Server work. But it does not change it back when Reporting Server is uninstalled. So the assembly cannot be loaded and the SSRS cannot respond
    our requests.
    Resolution:  When the Reporting Server is installed, the old web.config and rsreportsserver.config
    files will be backed up to web.config1 and rsreportsserver.config1. So you just need to change the files’ name back, then try to install Reporting Server of SCOM again. Everything would go smoothly. 
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi AakashGhare,
    According to your error message, SQL Server 2008 databases are version 655. SQL Server 2008 R2 databases are 661. When you are trying to attach an 2008 R2 database (v. 661) to an 2008 instance and this is not supported. As other post, once the database has
    been upgraded to an 2008 R2 version, it cannot be downgraded. You'll have to either upgrade your 2008 SP2 instance to R2, or you have to copy out the data in that database into an 2008 database (such as using the data migration wizard).
    In addition, if you want to use a Windows Batch file code and command to automatically login to SQL Server, detach database and attach a new one database, there is a similar details about batch code for attaching database to a new database, you can refer
    to this article.
    http://notesbyparth.wordpress.com/2012/06/29/run-sql-commands-from-windows-batch-file-or-attachdetach-database-automatically-using-batch-script/
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Error: Unable to communicate with the Reports Server

    The configuration I am working with is:
    * Oracle 8.1.6 DB on a Unix machine
    * Oracle Reports 6i on an NT machine
    * Microsoft IIS web server
    I have successfully tested my reports during the development phase of my project. Unfortunately, now that it is considered production and is available to upwards of 30 people, I am getting the following error message after verifying the server is up and after a numerous reports have been served:
    Error: The requested URL was not found, or cannot be served at this time.
    Oracle Reports Server CGI - Unable to communicate with the Reports Server.
    After receiving this message I noticed that the Report Server service is down and the log only indicates that it "shut down immediately". (no ORA messages) I tried restarting the service, but after serving one report, it would shut down again with the same message.
    I am wondering if it is a problem related to the cache. I used the default of 50M in the config file, but when the cache directory reaches 50M, the problem seems to appear. I then deleted approx. 30M of files from the cache directory and the Report Server service appeared stable. I changed the cache limit to 1M to see if there was a problem with the cache being so big. All appeared well for the first few hours of operation but then the Report Server service shut down again and upon restart crashed within a minute or two (usually as someone tests a report, it crashes again).
    Do I have a configuration problem? Has anyone seen this problem? Thanks in advance.

    Hi,
    I just found out that if i give
    http://localhost/cgi-bin/rwcgi60.exe?key1
    where key1 is a key mapping file that contains the report name,username and pwd for the database and desformat...etc..
    the report pulls out fine with the correct data..
    i am stunned...
    while none of the other commands like
    http://.../rwcgi60.exe
    or
    http://..../showenv?server=repserver
    or any other usual command doesnt work...
    anybody faced this before??
    Thanks.

Maybe you are looking for