Difference between revisions of "Information Systems:WebSmart Internal Server Error"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
One reason for this error is that the server is taking too long to perform the requested task; for example reading all warehouse transactions to build the item onhand values at year end. Press the browser back arrow to return to the page. Your session will no longer be busy, BUT THE SERVER IS STILL PROCESSING YOUR REQUEST. The example given takes about 15 minutes to run. Do NOT click on the search button again, but you can click on a column heading. This will read the work file that the server is building (or will be building once all the transactions have been read). When the server job is completed, you will be able to see the work file. |
One reason for this error is that the server is taking too long to perform the requested task; for example reading all warehouse transactions to build the item onhand values at year end. Press the browser back arrow to return to the page. Your session will no longer be busy, BUT THE SERVER IS STILL PROCESSING YOUR REQUEST. The example given takes about 15 minutes to run. Do NOT click on the search button again, but you can click on a column heading. This will read the work file that the server is building (or will be building once all the transactions have been read). When the server job is completed, you will be able to see the work file. |
||
| + | |||
| + | [[Category: WebSmart Problems]] |
||
Revision as of 09:11, 30 June 2016
One reason for this error is that the server is taking too long to perform the requested task; for example reading all warehouse transactions to build the item onhand values at year end. Press the browser back arrow to return to the page. Your session will no longer be busy, BUT THE SERVER IS STILL PROCESSING YOUR REQUEST. The example given takes about 15 minutes to run. Do NOT click on the search button again, but you can click on a column heading. This will read the work file that the server is building (or will be building once all the transactions have been read). When the server job is completed, you will be able to see the work file.