Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Foreground locking error on scheduled integration

Status
Not open for further replies.

Luvsql

Technical User
Apr 3, 2003
1,179
CA
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 because "Great Plains is still in the process of launching when the Integration Manager starts running." 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. It defeats the whole purpose of a scheduled integration when I have to manually re-run each integration every morning.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top