You are viewing limited content. For full access, please sign in.

Question

Question

Server type error

Workflow Version 11 Import Agent
Updated February 10
asked on February 10

Has anyone come across an error like the one below?  If so, may I have tips on resolving the issue?

 

'A network-related or instance-specific error occurred while establishing a connection to SQL Server.  The server was not found or was not accessible.  Verify that the instance name is correct, and that SQL Server is configured to allow remote connections.'

 

We are running Laserfiche 11, and I am seeing this error in the Workflow Administration Console 11 Error Log.

0 0

Replies

replied on February 10

If there are any other databases on that server, are they inaccessible as well? What have you tried so far? That error seems to indicate there's an issue with the SQL server that hosts your Workflow database. First step would be to login to that server and look for issues (check Windows event log, check disk space, check that the SQL server service is running, etc.).

0 0
View 1 previous reply
replied on February 10

Note that if Workflow itself appears to be working, the error message may refer to a connection failure for a SQL Data Source External Object (external database Workflow can query with activities). Ref: Workflow Data Sources Node

0 0
replied on February 10

Kevin, thank you for the response.  I logged into the server and checked the event log and am seeing a lot of errors with source 'Laserfiche Workflow Subscriber' and a lot of warnings with source 'CertificateServicesClient-AutoEnrollment' -- certificate for local system with Thumbprint 'aa bb cc etc...' is about to expire or already expired.  I apologize, I am new to Laserfiche and am unsure how to proceed.  I hope this provides more context.

Samuel, thank you for the response.  Workflow does appear to be working.  It seems only this one workflow is erroring.

0 0
replied on February 10 • Show version history

You can ignore the "CertificateServicesClient-AutoEnrollment" errors for this - they are not Laserfiche related. 

The Workflow Subscriber errors are separately of interest. However, they are not involved with the SQL error, as Workflow Subscriber does not interact with SQL. What are the Workflow Subscriber error messages?

As Workflow itself is generally functioning and only one Workflow is erroring, the SQL error is almost certainly about a connection to an external Data Source. Here's an easy way to find which data source Workflow can't connect to:

  1. Open Workflow Administration Console and connect to the Workflow server.
  2. Navigate to the External Objects > Data Sources node
  3. Under Actions, select Manage Data Sources...
  4. Select the first data source in the list, the select the Test button. Workflow will attempt to connect to that data source. Note the result if it is anything other than "Successfully connected to the data source."
  5. Repeat running Test on each data source in the list.
  6. One or more of them will likely return an error.
  7. Inspect the properties of any data source that fails to connect and check for any configuration values that may not be valid.

 

Screenshot of the Workflow Administration Console 12 Data Sources interface. The Workflow Administration Console 11 Data Sources interface looks the same.

0 0
replied on February 10

Samuel, this is a fantastic help.  It errored out on the database that I am having issues with.  I now have something to run with.  Thank you so much!

1 0
replied on February 10

There is not enough information to diagnose. The full error message might help tell us which component of Workflow is running into this error, which would give the investigation more direction. 

0 0
replied on February 10

Miruna, thank you for the response.  I apologize, I am new to Laserfiche and this role and am unsure what I can and cannot share.  One part of the error message I can add is 'error:40 - Could not open a connection to SQL Server'.  I logged into the SQL server and everything looks fine.  I think this may be a Workflow issue.  I did notice these errors started when a cumulative update for Windows Server failed to install.

0 0
replied on February 10 • Show version history

No apologies needed.

Where you look at the errors in the Workflow Admin Console, you'll see a pane that shows details. The part under <StackTrace> tells us which part ran into issues.

 

If you're looking at it in the Event Viewer, it should have similar information.

As for information you'd be giving away, it would have the machine name and the WF server service user name (as Thread Identity or Windows Identity). If you're not comfortable sharing that, your solution provider can open a case with Tech Support and provide it that way.

If this started after a Windows update, it's possible that SQL Server just didn't start, so I'd look at Services first.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...