|
JWait
Junior Member
USA
68 Posts |
 Posted - 10/31/2009 : 12:56:51 PM
|
What would cause the External Stack Controller to periodically loose the "path" in the "Order File Management" under the "Order Manager Data Files" tab in the settings?
When I noticed this has happened, I shut down the Stack Controller and restart it. At that time there are a list of Website Updates that have not been run. When I click the "send now" button it seems to send them ok. I'm just wondering what causes it to "lose the path" to begin with.
We use the stack controller for web site updates only, no email is sent, ever. |
SEOM+POS 5.609
Vista Ultimate 64 bit
Access 2007
Highly modified x-cart 4.1.10 web site
Trying to upgrade to x-cart 4.2.3 but getting SEOM errors |
|
|
Mark Setzer
Administrator
USA
1752 Posts |
Posted - 11/02/2009 : 12:46:57 PM
|
Support can help but you're describing the effects of a bug in the current ESC release when a new workstation sends its data for a given data file for the first time. It must "register" w/ the Stack (adding workstation-specific data to a table called OMFileLocations and displayed on that tab). Records added to the queue tables must always refer to a workstation definition in that table by ID number.
If the stack is processing records associated with a given "FileID" for the first time, it will attempt to parse through the workstation data and determine how to connect to that workstation's data file. The bug comes into play when this data is re-loaded after the Stack tries to make sense of it and form an ADO.NET connection string - frequently this fails, even though the correct connection string is in the table. An error like "file ID 9 not found" might appear in the log. Restarting the stack should clear the error and reload the new file info from the DB on startup.
So as to why you are getting multiple new (blank) entries, the possible reasons are:
- data file-specific connection info has changed (new server? new database name? multiple data files?)
- workstation itself is new (not present in OMFileLocations)
- workstation-specific info has changed (new machine name? new DSN name for Order Manager?)
...but they should basically resolve themselves if you restart the stack after you notice this behavior. |
Mark Setzer
Stone Edge Technologies, Inc. |
 |
|
Losing the Path
