Run a failed Frontweb order: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''**this should be done by a network administrator, not a technician**''' | |||
In the rare event that an order cannot be processed by Frontweb (i.e., hotfolder hard drive full, dongle not found, etc.), you will need to re-run the order by using the "processorder" command. | In the rare event that an order cannot be processed by Frontweb (i.e., hotfolder hard drive full, dongle not found, etc.), you will need to re-run the order by using the "processorder" command. | ||
Latest revision as of 16:42, 10 June 2013
**this should be done by a network administrator, not a technician**
In the rare event that an order cannot be processed by Frontweb (i.e., hotfolder hard drive full, dongle not found, etc.), you will need to re-run the order by using the "processorder" command.
Note: The order will still need to be active in the Frontweb temp directory to work.
- On the Frontweb computer, open a Windows Command Prompt (Start->Run->cmd).
- Enter: cd..
- Enter: cd..
- Enter cd frontweb
- Enter cd engine
- At this point, you should now be at your Frontweb Engine folder on the local computer.
- Enter the following command string:
express.exe processorder 1000 express
(motor name)(command)(order number)(instance)
motor name= express.exe (standard)
command= processorder (standard)
order number= the failed order number within Frontweb
instance= prefix, thetaweb, express, design, or whatever you have defined your Frontweb instance to be named in the database.
8. If the order is able to re-run, it should show up immediately in your Frontline hotfolder (as with all new orders).