I am using CRM Dynamics 2013, updates were performed on the server over the weekend, and when I try and browse the server I get the following error message:
The initialization of the CRM authentication pipeline execution has failed for org crm-mbtgroup.tarsus.co.za with a sql error: Server: sql server name, Exception: System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'p_GetCrmUserId'.
This gives me a 404 exception when I try to browse the server, any ideas>
I resolved this issue, This issue occurred due to Update roll-up for CRM Dynamics not being successfully applied, therefore I dropped all the stored procedures in the MSCRM_Config and then repaired my installation and the installation re-created the procs for me, I restarted all necessary CRM services and everything worked fine again
Related
I have a task to run an SSRS report and export it to a folder in c drive. For the effort I tried to come up with below. I am running the statement below on the server where SSRS is installed. I want to be able to run this both on management studio as well as a job. Data driven subscriptions are not allowed for some internal reasons. So I had use XP_CMDshell.
I got the PrintPdfreport.exe from another team that is already using this functionality.
Exec master..XP_CMDSHELL 'C:\PrintPdfReport.exe "http://ServerName/Reportserver?/CIP Reporting/CIP Dashboard&rs:Command=Render&rs:Format=PDF" c:\Reports\DailyCIPDashBoard_20181029091327.pdf'
I am getting the access/authentication 403 error below. I am not sure how I can resolve this.
Output With Error below
Unhandled Exception: System.Net.WebException: The remote server
returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at PrintPdfReport.Program.Main(String[] args) NULL
Assign the SQL Server service to run under an AD account (Domain\serviceaccount). Once you have that then add the account to reporting services with Browser access.
And grant that account read/write access to your target folder as well.
I have created a ssis package to load data from server 1 table1 to server 2 table2. This package is running fine inside the business intelligence studio. But the issue is , when I schedule this package in SQL server agent as a job, the package execution is failing.
The error I am getting is
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. Description: "Login failed for user 'Domain\Server1$' .
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "Server2.Database2" failed with error code 0xC0202009.
Please help me to fix the issue. I am using SQL Server 2014
Thank you very much for your time and help!
This is a security / permissions issue. Update the SQL Server Agent job to use an account which has sufficient permissions to complete all of the actions inside the SSIS package.
Explanation
The package completes succesfully when executed from Business Intelligence Studio, because that execution is running under you credentials. It is running as you. When you run the package from SQL Service Agent job, it is NOT using your credentials. Instead it is using account 'Domain\Server1$' and that account does NOT have sufficient rights against Server2.Database2 to complete all of the package actions.
To solve this, you could update the security on Server2.Database2 and allow 'Domain\Server1$' to perform the same actions as you, but that is unadvised. Instead, best practice here is to establish an SSIS proxy account. Here is a good article discussing how to go about that. After you have established this proxy account, grant the new proxy account sufficient permissions to complete the actions inside of your SSIS package and your error message will go away. Hope this helps!
I'm trying to copy a database to another server. I've successfully done this with these two servers several times, the last time was just a few days ago. However, now when I try to execute it, I get an error:
TITLE: Copy Database Wizard
------------------------------
Start failed for Job 'CDW_xxxx_SGSTG51DBA01_13_2'.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch
(Microsoft.SqlServer.ConnectionInfo)
------------------------------
SQLServerAgent is not currently running so it cannot be notified of this action.
(Microsoft SQL Server, Error: 22022)
Base on this information, I immediately checked that SQL Agent was running. It wasn't, so I started it. I ran it again, but got the same error. I then double checked that the login information provided for both the source and destination servers was correct. It was.
So I'm now getting this error with verified connection information and SQL agent is running. What else could be causing this problem? Does the account running SQL agent need access to both servers?
I have created one SSIS package which is I have imported into Integration services MSDB
which is executed correctly from Integration services MSDB
But when I tried to create a JOB in SQL Server Agent and try to execute
that job it is giving me following error
I'm unable to get it what is wrong from following error
please help me.
(I have tried by adding config file and deleting config file when I add packge in SQL Server Agent)
Message
Executed as user: cam\Package.Runner. Microsoft (R) SQL Server Execute Package Utility Version 10.0.4000.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 5:05:01 AM Error: 2013-07-02 05:05:01.85
Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Property" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2013-07-02 05:05:01.85
Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error
Error: 2013-07-02 05:05:02.02
Code: 0xC0202009 Source: BloombergFTP Connection manager "WOPR\Fireball_PROD.sa" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'package.runner'.". End Error Error: 2013-07-02 05:05:02.02 Code: 0xC00291EC Source: Execute SQL Task Goodhart Execute SQL Task Description: Failed to acquire connection "WOPR\Fireball_PROD.sa". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:05:01 AM Finished: 5:05:02 AM Elapsed: 0.266 seconds. The package execution failed. The step failed.
Ensure that credential used by "WOPR\Fireball_PROD.sa" BloombergFTP Connection manager is valid before trying the following.
Either
Change the SSIS Package ProtectionLevel property to
EncryptSensitiveWithPassword and Set the Packagepassword if you want
to encrpt the package.Specify this Password at command line in
SQLSERVER Agent Job SSIS configuration.
Change the SSIS Package ProtectionLevel property to DontSaveSensitive if you dont want to encrpt the package.Specify the credential in the SQLSERVER Agent Job SSIS configuration itself.
I ran into a similar problem. My SSIS package was running within SQL Data Tools without errors, but failed within SQL Server Agent, using a admin proxy. Looking into the logs of the job, the error message was something like "Failed to decrypt protected XML node "DTS:Property""
One of the many possible reasons (next to the one given by S.M.) for such an error is that the proxy doesn't have access to tables/databases you're referring to, while you yourself do have access to these tables.
In my case: I was writing stuff to a personal database which couldn't be accessed by the credentials underlying the proxy. Hence, when running the SSIS package within SQL Data Tools, I could access the tables, but when running the job within SQL Server Man. Studio, I couldn't. I changed the destination database of my package and the job could be runned.
This might be helpful for more people running into similar problems.
The company I work for has locally a MS Server 2005, with SQL server 2005. The problem that they are facing is that although they can log in to their platform and do most of the things they want (like importing data into the database, editing etc.) they get the message below when they are trying to get a report:
Reporting Services Error: The Report Server has encountered a configuration error; more details in the log files (rsServerConfigurationError)
In the log file I can't find any error or any change. What should I do?