Hi John_Simmons,
The site recommended to send you a personal message, I hope that’s ok for you.
I have installed ServiceControl primary instance and ServiceInsight on the same server. Because it is a core server, I can not install ServicePulse out of the box. On the same server the software is running which sends MSMQ messages.
The problem I have now is that retrying a failed message stays in the Retry requested mode. Do you have an idea where to search what’s going wrong? I can’t get a clue from the log files.
enclosed is the log file of the ServiceControle instance. I started the retry at June 10 15:13
The conversation id of the retried message is 029a647b-d83e-42a9-a733-b18b00fa93a2
The logs show that ServiceControl is trying to save poison messages in the error queue to disk. These messages seem to be missing the NServiceBus.FailedQ header which is required. Can you confirm that the messages you are retrying contain that header?
Are you sending any messages directly to the error queue?
Some of the exceptions in the log file you provided indicate that the D:\ProgramData\Particular\ServiceControl\Particular.ServiceControl\Logs\FailedImports\Error\FailedErrorImports\ directory does not exist.
Can you confirm whether or not you see that directory? If so, could you provide one of the files in it?
If the directory does not exist, can you restart the ServiceControl instance and confirm that it gets created.
Just checking back to see if your questions have been answered. If I don’t hear back from you in a couple of days I’ll assume that “no news is good news”, and close this case. If you need any further information or assistance, email us at “Support@particular.net” with the details and our support team will be happy to assist.