I have a scheduled integration setup that first runs the login to GP, then an integration group (2 AR integrations). I have them set at 5 minutes apart.
The TK article for this particular error says that the error is becuase "Great Plains is still in the process of launching when the Integration Manager starts running." However, I then increased the time to 15 minutes apart and finally at 30 minutes apart, but the first record of both
integrations still fails with this error "could not set foreground locking value to 0."
How can I get rid of this error? It only takes less than a minute to completely log into GP. There aren't any other occurences of the Dynamics.exe running either.
The TK article for this particular error says that the error is becuase "Great Plains is still in the process of launching when the Integration Manager starts running." However, I then increased the time to 15 minutes apart and finally at 30 minutes apart, but the first record of both
integrations still fails with this error "could not set foreground locking value to 0."
How can I get rid of this error? It only takes less than a minute to completely log into GP. There aren't any other occurences of the Dynamics.exe running either.