Automation Suite Migration: Database Catalogue Update

News Knowledge Base
,
1

After migrating from Orchestrator standalone to Automation Suite, error seen when trying to access Orchestrator: Unhandled exception. Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid object name 'ta.SystemSchedules'.

Issue Details:

The present concern pertains to the migration of Orchestrator standalone to the Automation Suite. Adherence to the provided guidelines and proper configuration of each step is crucial. However, an oversight occurred during Step 6, specifically the omission of updating the catalogue name, which subsequently led to the manifestation of an error.

Upon examination of the connection string, it becomes evident that the Initial Catalog directs to the Automation Suite Orchestrator rather than the Standalone database.

E.G.:

Default: Server=ServerName,1433;Initial Catalog=AutomationSuite_Orchestrator;Persist Security Info=False;User Id=######;Password=######';MultipleActiveResultSets=False;Encrypt=False;TrustServerCertificate=False;Connection Timeout=30;Max Pool Size=100;



Resolution:

It is recommended to modify the connection string such that it points to the appropriate migration database. This adjustment should successfully resolve the complication.


Refer the Automation Suite - Full Installation Migration details.