Syspro Connection Test fails through FlowGear DropPoint - flowgear

When testing my newly-configured Syspro connection to work through a DropPoint, I get the following error:
(Syspro 1.0.0.2) Message queue client closed!
What am I missing?
EDIT:
More info:
Now that I'm testing a previously-working (about a week ago) SQL Watcher on the same DropPoint I'm getting an error:
The Node SqlWatcher (v2.1.0.4) could not be initialized.

Related

Repeated Error in SQL Server 2017 Error Log (Error: 15404, error-code 0x5)

I'm relatively new to SQLServer2017 Developer and System Center Operations Manager however I was asked to set up a SCOM test environment for our network. However, I keep receiving this error about one of my SCOM service accounts. I have already looked at some fixes and applied them however after refreshing the log the same error message still keeps appearing.
2020-02-13 14:03:09.05 spid47s An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'OMDASTest', error code 0x5.

Botium jobs stucked at ready

All my Test Project are stuck on "Ready".
I tried restarting containers and even "I'm Botium" is stuck on Ready without passed/failed results.
Job Log is here: https://pastebin.com/851LPCBS
In the Docker logs is:
2019-10-04T08:25:30.046Z botium-box-worker sending heartbeat ...
2019-10-04T08:25:30.049Z botium-box-server-agents agent.heartbeat: {"title":"heartbeat from agent b0c5b43c0f82 for group Default Group","name":"b0c5b43c0f82","group":"Default Group"}
2019-10-04T08:25:35.559Z botium-box-server-index WARNING: a socket timeout ocurred. You should increase the BOTIUMBOX_API_TIMEOUT environment variable.
2019-10-04T08:25:35.598Z botium-box-server-index WARNING: a socket timeout ocurred. You should increase the BOTIUMBOX_API_TIMEOUT environment variable.

okhttp 3.7.0 SSL Shutdown failed threw UnknownHostException and not SSLException

While making a network request with low connectivity very rarely I see that I get
<-- HTTP FAILED: java.net.UnknownHostException: Unable to resolve host ....
while my server seems to have got the request correctly. I found 1 instance of it with device logs which shows actually an SSLException happened
D/NativeCrypto: jniThrowException: javax/net/ssl/SSLException: Read error: ssl=0x7dc365f080: I/O error during system call, Software caused connection abort
D/NativeCrypto: jniThrowException: javax/net/ssl/SSLException: SSL shutdown failed: ssl=0x7dc365f080: I/O error during system call, Broken pipe
My question is why does okhttp and retrofit throw UnknownHostException and not SSLException, and is there a way to actually get the SSLException as currently my app thinks the request did not go while server processes that request.
I am using
okhttp:3.10.0
retrofit:2.2.0
adapter-rxjava2:2.2.0

Labview Instrument Error: A service request has not been received for the session

I'm trying to get a Labview VI working. However, I'm getting an error on the KE6485 Multi-read sub-VI with the error "Driver Status: (Hex 0xBFFF004A) Error - A service request has not been received for the session". Does anyone have a suggestion on steps I could take to fix this?

FlowGear Droppoint error

I'm getting the following error when trying to Test a SQL connection via a droppoint:
DropPoint Invoke Error: Unable to instance node SqlQuery 2.1.0.6:
Decryption failed: Padding is invalid and cannot be removed.
How do I fix this?
This indicates that either the transport or the stored Node at the DropPoint is corrupt. A DropPoint restart should resolve this but it's strongly recommended that you upgrade to the new WebSockets-based DropPoints which can be downloaded from the Console. More at https://developers.flowgear.net/kb/DropPoint