The SQL Clone Agent 2.3.5.8332 service to start in 00:00:45 in AWS

Sergei

Subscribers to Red-Gate products.

Environment: win Server 2016 DataCentre.
Trying to setup environment for cloning in a on-premises data centre and in the cloud.

Download and installed SQL Clone agent.
When setting up agent via UI with a windows account got error: "The SQL Clone Agent 2.3.5.8332 service to start in 00:00:45 in AWS".
However, in the services console SQL Clone Agent is shown as running.

Error in the windows system log:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT SERVICE\MsDtsServer110 SID (S-1-5-80-1770670200-1234090253-3451813168-4041049723-2370973757) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Permissions were set but in the component services but still the same error.

Please advise as a trial period will expire soon.

Regards,
Sergei

Mark R

Is the SQL Clone Agent working, despite the errors? What Windows username is it running as?

Regarding the error in the system log - it mentions user "NT SERVICE\MsDtsServer110", so that sounds like it's related to SQL Server 2012, not the SQL Clone Agent.

Sergei

Hi Mark,

Yes, it is working but I am not sure if a SQL Clone agent fully functional.
The above error happens when I was trying to initialize a sql clone agent.
MsDTs was restarted under domain account and that error gone.
However, windows log still shows errors related to SQL Agent Clone with no description - see below.

The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
RedGate.SqlClone.Setup.Common.ServiceFailedToStartException: The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
at RedGate.SqlClone.Setup.Common.ServiceManager.WaitForServiceStarted(ServiceController sc, TimeSpan timeout)
at RedGate.SqlClone.Setup.Common.ServiceManager.StartupService(String serviceName, String[] parameters)
at RedGate.SqlClone.Agent.Setup.Model.PostInstallSetup.<Setup>d__3.MoveNext()


>>Windows username is it running as?
It is running as domain_name\XXX_xxxxx_xxxx_xxx. This account has local admin rights on the box.

Is there any error log I could open and check?
Where could I increase timeout value?

Clicking on "System" in windows opens a system info dialog which reads "Windows Server 2016 Datacenter".

Regards,
Sergei

Sergei

FYI.
Powered up a new instance of Windows Server Datacentre 2016 not joined to domain.
Tried to initialize SQL Clone Agent under local administrator account.
Got the same error as before:

The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
RedGate.SqlClone.Setup.Common.ServiceFailedToStartException: The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
at RedGate.SqlClone.Setup.Common.ServiceManager.WaitForServiceStarted(ServiceController sc, TimeSpan timeout)
at RedGate.SqlClone.Setup.Common.ServiceManager.StartupService(String serviceName, String[] parameters)
at RedGate.SqlClone.Agent.Setup.Model.PostInstallSetup.<Setup>d__3.MoveNext()

Sergei

FYI.
Powered up a new instance of windows server 2012 with SQL server 2016 in AWS.

The same error:

The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
RedGate.SqlClone.Setup.Common.ServiceFailedToStartException: The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
at RedGate.SqlClone.Setup.Common.ServiceManager.WaitForServiceStarted(ServiceController sc, TimeSpan timeout)
at RedGate.SqlClone.Setup.Common.ServiceManager.StartupService(String serviceName, String[] parameters)
at RedGate.SqlClone.Agent.Setup.Model.PostInstallSetup.<Setup>d__3.MoveNext()

However, on the dashboard the SQL clone agent marked as a green. Will make a firewall change tomorrow and try making a clone.

Regards,
Sergei

Mark R

Thanks for getting back to me with more info.

It sounds like the agent is working correctly, but it taking longer to start than we normally expect. If you restart the SQL Clone Agent service, how long does it take to start?

Sergei

it takes around 55 seconds.

Dan B

Hi Sergei,

Are you able to get your clone server and agent logs from https://documentation.red-gate.com/clone2/troubleshooting/log-locations and forward these on to support@red-gate.com please?

Sergei

Hi Mark,

Yes, it is working but I am not sure if a SQL Clone agent fully functional.
The above error happens when I was trying to initialize a sql clone agent.
MsDTs was restarted under domain account and that error gone.
However, windows log still shows errors related to SQL Agent Clone with no description - see below.

The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
RedGate.SqlClone.Setup.Common.ServiceFailedToStartException: The SQL Clone Agent 2.3.5.8332 service failed to start in 00:00:45.
at RedGate.SqlClone.Setup.Common.ServiceManager.WaitForServiceStarted(ServiceController sc, TimeSpan timeout)
at RedGate.SqlClone.Setup.Common.ServiceManager.StartupService(String serviceName, String[] parameters)
at RedGate.SqlClone.Agent.Setup.Model.PostInstallSetup.<Setup>d__3.MoveNext()

Are you able to reproduce the error in AWS on your end? It shouldn't take much time.

>>Windows username is it running as?
It is running as domain_name\XXX_xxxxx_xxxx_xxx. This account has local admin rights on the box.

Is there any error log I could open and check?
Where could I increase timeout value?

Clicking on "System" in windows opens a system info dialog which reads "Windows Server 2016 Datacenter".

Regards,
Sergei

Dan B

Hi Sergei,

If the clone agent is creating clones then it is fully functional. The 45 second error can occur when the agent is starting but it can still be responsive after this time.

The team are aware that this occurs but currently a full workaround hasn't been put in place. I will keep you updated with any progress on this.