• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Error "asio async_connect error asio.system:10061" starting InDesign Server

Explorer ,
Dec 29, 2022 Dec 29, 2022

Copy link to clipboard

Copied

Anyone seen this before, or have ANY suggestions?

 

Currently running IDS 2021 (v17). No issues. Created a package for IDS 2022 (V18) and installed. When we run the V18 "InDesignServer.com -configuration test1" from the command line (to ensure all is working correctly), all looks good, but then we get:
[2022-12-29 10:19:56] [info] asio async_connect error: asio.system:10061 (No connection could be made because the target machine actively refused it.)
[2022-12-29 10:19:56] [info] Error getting remote endpoint: asio.system:10057 (A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.)
[2022-12-29 10:19:56] [error] handle_connect error: No connection could be made because the target machine actively refused it.

We do NOT have this problem on the same physical box, running the SAME command line again V17. I have searched for instances of this error, to no avail.

TOPICS
Activation billing and install

Views

2.6K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , Jan 30, 2023 Jan 30, 2023

I finally heard back from Official Adobe Support.  Apparently this is a KNOWN issue that affects some InDesign V18 installations.  It has so far happened on BOTH of ours.

We have been told we can safely ignore the errors, and a future version should remove the errors...  Of course no ETA on the next release.

 

Paul

Votes

Translate

Translate
Community Expert ,
Dec 31, 2022 Dec 31, 2022

Copy link to clipboard

Copied

https://think-async.com/Asio/

 

Looks like some part of InDesign Server is using it - directly or indirectly.

REST Api ? 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 30, 2023 Jan 30, 2023

Copy link to clipboard

Copied

I finally heard back from Official Adobe Support.  Apparently this is a KNOWN issue that affects some InDesign V18 installations.  It has so far happened on BOTH of ours.

We have been told we can safely ignore the errors, and a future version should remove the errors...  Of course no ETA on the next release.

 

Paul

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 20, 2023 Jul 20, 2023

Copy link to clipboard

Copied

Latest update.  The next version did remove the error.  But now,  the latest version brought the error back.   Ignoring the error seems to be ok..

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 21, 2023 Jul 21, 2023

Copy link to clipboard

Copied

I can confirm that it is back.

I was solved in InDesign Server 18.2.1 and it is back in the latest release of InDesign Server, 18.3.0. Pretty weird. And indeed, we can ignore these errors, although they look pretty alarming. With InDesign Server 18.3.0 we get:

InDesignServer.com -port 120231
================================================================================
.  InDesign Server Version 18.3 x64
.  Copyright 1999-2022 Adobe Inc. and its licensors.
.  All rights reserved. See the other legal notices in the ReadMe.
================================================================================
Thu Jul 20 14:24:26 2023 INFO   [server] Initializing
Thu Jul 20 14:24:26 2023 INFO   [server] Loading the application
Thu Jul 20 14:24:26 2023 INFO   [server] Restoring Object Model
Thu Jul 20 14:24:26 2023 INFO   [server] Scanning for plug-ins
Thu Jul 20 14:24:26 2023 INFO   [server] Initializing plug-ins
Thu Jul 20 14:24:26 2023 INFO   [server] Starting up Service Registry
Thu Jul 20 14:24:27 2023 INFO   [server] Executing startup services
Thu Jul 20 14:24:27 2023 INFO   [server] Using configuration configuration_120231
Thu Jul 20 14:24:27 2023 INFO   [server] Initializing Application
Thu Jul 20 14:24:27 2023 INFO   [server] Completing Initialization
Thu Jul 20 14:24:27 2023 INFO   [server] Image previews are off
Thu Jul 20 14:24:27 2023 INFO   [server] Server Running
Thu Jul 20 14:24:27 2023 INFO   [javascript] Executing File: D:\Program Files\Adobe\Adobe InDesign Server 2023 - 1830\Scripts\startup scripts\ConnectInstancesToESTK.js
Thu Jul 20 14:24:27 2023 INFO   [javascript] Executing File: D:\Program Files\Adobe\Adobe InDesign Server 2023 - 1830\Scripts\converturltohyperlink\startup scripts\ConvertURLToHyperlinkMenuItemLoader.jsx
Thu Jul 20 14:24:27 2023 INFO   [javascript] Executing File: D:\Program Files\Adobe\Adobe InDesign Server 2023 - 1830\Scripts\converturltohyperlink\ConvertURLToHyperlinkMenuItem.jsxbin
Thu Jul 20 14:24:27 2023 INFO   [soap] Servicing SOAP requests on port 120231
[2023-07-20 14:24:28] [info] asio async_connect error: asio.system:10061 (No connection could be made because the target machine actively refused it.)
[2023-07-20 14:24:28] [info] Error getting remote endpoint: asio.system:10057 (A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.)
[2023-07-20 14:24:28] [error] handle_connect error: No connection could be made because the target machine actively refused it.

 And then it just works. We reported the issue to Adobe directly and hopefully it will (and stay...) resolved in upcoming versions.

-- Carlo 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 21, 2023 Jul 21, 2023

Copy link to clipboard

Copied

LATEST

Yep, that is the SAME error we are getting (again) with 18.3.  Just like you, it went away with 18.2.x, but with 18.3 it came back...  Apparently someone put in a "patch" for 18.2.1 but forgot to roll it into the main branch...

It would be nice to not have to "ignore" errors..  🙂

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines