Process/export problem - getting ImgCoreSocket error
Sometime within the last week, I can no longer process/export images, I get this error message: ImgCoreSocket error (10060) after a little while where C1 tries to export, then followed by a box advising me to restart C1.
I started by following the on-screen advise; first restart C1, then restart PC - didn't help.
Thinking it might be a anti-virus problem I have allowed C1 full permission and subsequently I tried disabling the anti-virus all together - didn't help.
De-installed C1, restarted the PC and re-installed C1 - didn't help (version 14.2)
Today I have tried de-installing again, clear all trace of C1 on the PC, run a cleaning program, restart the PC and install C1 version 14.4.1.6 - didn't help
I don't know what to do now, does anyone have a suggestion?
Running Win10, version 10.0.19043 build 19043
-
I found a solution.
Like the gentleman in this thread, I found that changing the ICC profile did the trick, I can now process/export again.
0 -
Søren,
Is it possible that the referenced ICC profile - probably a default picked up from one of several possible sources on the PC - had become unavailable at that location? In which case changing the referenced ICC profile in the Output Process definition might resolve the problem?
0 -
I think it sounds like a really good and plausible explanation.
It is just strange that I haven't changed anything in my setup, nor done any updates. If this is the case (and it sounds like it) I find it strange, unless the program makes updates/changes when I start it, without me prompting for it.
Now, I didn't pay attention to the ICC profile when I changed it, and I don't remember what it was called, but I now have three greyed out profiles in the selection box; Gray, RGB and CMYK - I might have had it set for RGB.
The "SRGB IEC61966-2.1" and "Adobe RGB (1998)" both work - I haven't tried other options, as I am quite happy that it is working again, and the result look as before :)
0 -
To check for the network issues, refer to the steps from Knowledge Base article 12333 and run socket test utility on both source and target.
If there are messages related to queue corruption in the target event_log, contact SharePlex Technical support for help in fixing the queue corruption.
If the error is related to the number of queues in replication, Shutdown SharePlex on Source and Target, increase the SP_QUE_MAX_QUEUES parameter to a higher number. Maximum number of queues per cop is 1024, it is controlled by SP_QUE_MAX_QUEUES parameter and default is 25.
0
Post is closed for comments.
Comments
4 comments