Error: Could not connect to http://localhost:8996/MetaPresenter TCP error code 10061 (2 replies)
I have resolved this issue. The .xml had been corrupted. I created the job again and no longer see this error.
Closed due to inactivity.
I have resolved this issue. The .xml had been corrupted. I created the job again and no longer see this error.
Closed due to inactivity.
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
I've been able return data with my Sage 300 connector from my WooCommerce reader all day when suddenly I get this error when I try to run preview mode (See screenshot). When this happens, the preview service in my admin panel switches off as well. When I turn it back on and refresh the transform, same error pops up and switches the service back off. I tried stopping and starting the IMan IIS application pool and restarted the services via the admin panel but the same thing happens.