W3001 connection refused [SOLVED]

OL Connect Professional Workflow
1

Hi,

I have this error :

W3001 : Error while executing plugin: Socket Error # 10061 Connection refused
Execute Data Mapping: W1603 : Plugin failed - 14:08:35 (elapsed time: 00:00:01:110)

It’s the DataMapper pluging

My credential are correct, use ol-admin with the default password, re-enter the password to be sure that it enter correctly but no luck.

In the Workflow/preference/behavior/ol connect, I enter also the good information, restart the service but still no luck. In this windows I have LocalHost as server address and port 9340.

It was working fine before I enter my new licence. I had an evaluation Licence before and was working fine but since I enter a valide licence not working. Maybe no link.

Someone can help ?

2

Can you check to make sure that your OL_Connect server service is up and running?

3

Thanks, it’s work !!

1 Like
4

Hello, I’m having the same error stand still even tho OL_Connect server service is running ! Thanks

5

Have you check that your Workflow credentials for the Connect Server matches those entered in the Connect Server?
In Workflow
In Connect Server / User
In Connect Server / Database connection

1 Like
6

I just did, and everything is matching but now i’m having this error,
[0002] W3001 : Error while executing plugin: {“error”:{“status”:401,“message”:“Failed to authorize with basic authentication provided. (SRV000100)”,“parameter”:“”}}
[0002] All in One: W1603 : Plugin failed - 13:57:14 (elapsed time: 00:00:00.192)

7

Check that in the All In Plugin doesn’t have different values in the OL Connect Proxy tab.

8

reply
reply1920×1080 408 KB

They’r exactly the same !

9

Do you have them setup in both your Workflow preferences and in that tab?

If so don’t.
Better to always have it setup only in the Preferences, unless you have specific Connect plugin you want to use a different Connect Server.

10

I just updated them only in preferences and nothing has changed … sorry for the inconvenient !

11

At this point, better you open a support ticket via our website so an agent can remote in and troubleshoot this with you.