Issue with ARS 7.4.3 upgrade from 7.3.1 after breaking replication and converting Pub to standalone. Config Manager loaded and returned instance related error

We upgraded the binaries for ARS 7.3.1 to 7.4.3 on our publisher host after breaking replication and demoting the pub.

On Launch of configuration manager - seeing the new DB names to be created, and clicking NEXT we get an error about an object not being set to a reference … or some such.

Not in the troubleshooting guide - and applying the appropriate hot fixes for 7.4.3 changed nothing.

opinions?

Parents

0 dyannic over 3 years ago

No luck on the in-place upgrade. The install log shows a failure akin to 'file not found' - when it gets to the starling configuration section.

We've been advised to go the new-install and import route. We've taken that path … upgrade begins.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 dyannic over 3 years ago

No luck on the in-place upgrade. The install log shows a failure akin to 'file not found' - when it gets to the starling configuration section.

We've been advised to go the new-install and import route. We've taken that path … upgrade begins.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

No Data

Endpoint Privilege Management

Issue with ARS 7.4.3 upgrade from 7.3.1 after breaking replication and converting Pub to standalone. Config Manager loaded and returned instance related error