SQL Server

WHEN PROBLEM POSSIBLE CAUSE CORRECTIVE ACTION
When any insert /update statement is executed Displays EXCEPTION_ACCESS_VIOLATION exception Microsoft issue Refer to following article:

https://support.microsoft.com/en-in/help/3103998

SQL Server Cluster enabled deployment

WHEN PROBLEM POSSIBLE CAUSE CORRECTIVE ACTION
The SQL Server Fail-over Wizard is executed on the cluster enabled SQL server.

All the IRC tasks fail or gets queued.

 Time lag due to the temporary SQL server unavailability during fail-over process.
  1. Restart the IRC services.
  2. Reschedule the IRC tasks.
The Fail-over Wizard is executed on the cluster enabled SQL server.
Note: This issue occurs if the report server database is a part of the cluster database and participates in the SQL server fail-over wizard.
The IRC reports are not accessible. The encryted key and the connection string are not available in the new primary database, after the fail-over process.
  1. Open the SQL Server Reporting Services Configuration Manager.
  2. Connect to the Listener (the name specified in the MSSRSS Server Name with Port number field when activating the IRC services).
  3. Delete the encrypted keys. A confirmation message is displayed.
  4. Click Yes. The encrypted keys are deleted. The Properties tab of the
    Note: If the system displays an error message, you must delete the encrypted keys manually. To delete the encrypted keys manually, login to the SQL server and execute the DeleteEncrytedContent stored procedure manually on the Report server database.
  5. Browse the Report Server.
  6. Click the IRC database and navigate to IRC > DataSources > CoreDB > Manage screen. The Properties tab is displayed.
  7. Specify the Connection string if not already populated. The connection string format must be:
    • data source=SQL server name;initial catalog=IRC Database name;Application Name = Infor Risk and Compliance
  8. Click Save and Apply.
  9. Execute the reports.
The Fail-over Wizard is executed on the cluster enabled SQL server.
Note: This issue occurs if the report server database is a part of the cluster database and participates in the SQL server fail-over wizard.
The schedule reports are not displayed on the Report subscription tab. The new primary database is not linked with the SQL Listener. Run the sp_addlinkedserver between the SQL Listener and the Report server.