Troubleshoot Issues

Problem

Error while trying to start ArchestrA Connector Client service, which was paused or stopped. The following error is logged while redeploying the Gateway object:

Error while trying to start ArchestrA connector client service, which was paused  or stopped. Error :System.InvalidOperationException: Cannot start service SkeltaConnectorClientArchestrA on computer '.'. ---> System.ComponentModel.Win32Exception: An instance of the service is already running

   --- End of inner exception stack trace ---

   at System.ServiceProcess.ServiceController.Start(String[] args)

   at System.ServiceProcess.ServiceController.Start()

   at Skelta.Runtime.Gateway.GatewayRuntime.CheckServiceStatus(Object nullParam)

Resolution

Undeploy the Gateway object and ensure that no errors are getting logged into the logger. Redeploy the Gateway object.

Problem

Inbound authentication user could not be validated in platform. The following error is logged while provisioning and deploying the Gateway object:

Inbound authentication user (SKELTANB26\John)  could not be validated in platform, this could affect the inbound connection from workflow server.Please provide valid user information and re deploy Gatewayobject.

Resolution

1. Ensure that the inbound information entered is correct.

2. If the user belongs to the local machine, enter Authentication User Domain as localhost instead of giving the machine name.

3. Click Save.

Problem

The given key was not present in the dictionary. The following error is logged while deploying the gateway object:

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

at System.ThrowHelper.ThrowKeyNotFoundException()

at System.Collections.Generic.Dictionary`2.get_Item(TKey key)

at Skelta.Connector.Proxy.SingletonProxy`1.ReCreateConnection(String multiHostSingleProxyIdentifier)

at Skelta.Connector.Proxy.SingletonProxy`1.GetConnection(String multiHostSingleProxyIdentifier, Boolean& isOldConnectionExpired)

at Skelta.Connector.Proxy.EngineProxy.GetChannel()

at Skelta.Connector.Proxy.EngineProxy.ConnectorRuntimeShutdown(String connectorPluginName, String uniqueEnvironmentName, String[] connectorContext, String repositoryName, String[]& error)

Possible Cause

The gateway object is initially deployed with machine name as the Server Address. The user redeploys the gateway object by changing the Server Address to either localhost or IP address.

Resolution

4. Undeploy the Gateway object.

5. Edit the Server Address as required and click Save.

6. Reauthorize and redeploy the Gateway object.

Problem

Authorization fails with the following error after entering the credentials when the Provider selected is Galaxy Users and none of the Gateway objects are deployed from that Galaxy to the same repository.

Resolution

Ensure that at least one Gateway object is deployed from this Galaxy to the same repository.

Problem

Page Not Found error or blank page in the System Platform IDE.

Possible Cause

‘--‘ prefix in the in the Enterprise Console site URL

Resolution

Remove the ‘--’ prefix while editing the Enterprise Console site URL in the workflow Gateway object.

Problem

"Could not connect to the Workflow Server..." error on Test Connection while connecting Galaxy to the Workflow Server.

Resolution

7. Turn off the Windows Firewall.

8. Ensure that the Workflow Engine service is running.

9. If the Workflow Engine service is not running, start the service. Check the message logged in the logger and note down the Port Number for further verification.

10. Enter the required information for Gateway Configuration.

11. In the Advanced tab of the Gateway Configuration, ensure that the Outbound Connector Port Number is same as the Port Number logged in the logger.

12. Click Test Connection and verify.

Problem

Slow response time from AttributeReadWrite object.

Possible Cause

Failed to acquire any type of license feature MXAccess_Runtime.

Resolution

Acquire a valid MXAccess_Runtime license on the node where the Workflow Gateway object is hosted.

Problem

The Enterprise Console menu does not load when you try to connect to the GR node through IDE, from a different server.

Possible Cause

The required files are not copied on the IDE node,therefore the Enterprise Console menu does not load.

Resolution

13. Open System Platform IDE, specify the GR node name and Galaxy name ,and connect to the galaxy.

14. Open Workflow Gateway Object and close it without saving.

15. Restart IDE and connect to the galaxy.

16. Go to Workflow - Toolbox

17. Select Workflow Gateway object from the dropdown.

18. The Enterprise Console menu is displayed.

Problem

The Enterprise Console page crashes in IDE with the message: Error decrypting the request (The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters).

Possible Cause

The DLL files are mismatched as they are not copied from the object location to the CustomCategoryUIFiles and IDEExtensions folders.

Resolution

Manually copy the connector DLL files from C:\Program Files (x86)\ArchestrA\Workflow\IDEExtension to:

• C:\Program Files (x86)\ArchestrA\Framework\FileRepository\CustomCategoryUIFiles

• C:\Program Files (x86)\ArchestrA\Framework\Bin\IDEExtensions

Problem

The page does not get displayed for InTouch OMI when the controls does not load.

Possible Cause

• The Workflow Gateway Object might be configured with a user that might not be available in the current provider.

• Browser caching issue.

Resolution

• Deselect all the checkboxes for Compatibility View Settings.

• Clear browser cache.

  To clear Chrome browser cache, go to Settings --> Clear browsing data --> Advanced tab, and then select Password and other sign-in data checkbox.

• Set User Authentication for Security Settings - Internet Options

  • For Internet

    Navigate to Custom Level --> User Authentication (scroll down towards end) --> Logon. Select Automatic logon only in Intranet zone option, and then click Ok.

  • For Local Intranet

    Navigate to Custom Level --> User Authentication (scroll down towards end) --> Logon. Select Automatic logon only in Intranet zone option, and then click Ok.

  • For Trusted Sites

    Navigate to Custom Level --> User Authentication (scroll down towards end) --> Logon. Select Automatic logon only in Intranet zone option, and then click Ok.

  • For Advanced Tab

    Select Enable Integrated Windows Authentication option.

Problem

On importing the Workflow Gateway Object .pkg file in the Upgrade environment, below errors are logged in aalogviewer:

System.MissingMethodException: Method not found: 'Void Skelta.WinForms.ExtendedWebBrowser.UIHostBase.set_OverrideTabAndDeleteKey(Boolean)'.

at ArchestrA.InTouch.SkeltaControls.Controls.BAM.BAMControl.InitializeComponent()

at ArchestrA.InTouch.SkeltaControls.Controls.BAM.BAMControl..ctor() Error in constructor BAM control

System.MissingMethodException: Method not found: 'Void Skelta.WinForms.ExtendedWebBrowser.UIHostBase.set_OverrideTabAndDeleteKey(Boolean)'.

at ArchestrA.InTouch.SkeltaControls.Controls.FillForm.FillFormControl.InitializeComponent()

at ArchestrA.InTouch.SkeltaControls.Controls.FillForm.FillFormControl..ctor()Error in constructor FillForm control

Probable cause

The IE Web Browser control is replaced by Microsoft Edge WebView2 control. Hence, the errors are logged because of caching after the upgrade.

Resolution

Clear the cache and restart System Platform IDE.

Problem

In System Platform IDE, if configured with AIM and provisioned with AIM repository, sometimes it prompts for AIM credentials on browsing Enterprise Console pages, and sometimes not.

Probable cause

There is no logout mechanism available in it, so it will take from cache and not prompt for AIM credentials.

Resolution

To access Enterprise Control pages, you must provide AIM credentials if prompted.