I had exactly the same issue, Cloned copy of our live IFS created for us by IFS.I replicated the path - c:\IFS\IFSDocMan\Temp - on the cloned server, but user is still getting “Bad Request” error. The sever cloned for us by IFS has the directory structure on the E drive.Is there not somewhere where the config of “DOCUMENT_TICKET_TEMP_PATH” can be changed within IFS Applications?
I had exactly the same issue, Cloned copy of our live IFS created for us by IFS. I replicated the path - c:\IFS\IFSDocMan\Temp - on the cloned server, but user is still getting “Bad Request” error. The sever cloned for us by IFS has the directory structure on the E drive. Is there not somewhere where the config of “DOCUMENT_TICKET_TEMP_PATH” can be changed within IFS Applications? For anyone else viewing this. I found the settings at Document Management > Basic Data > Document Basic > Document Default Values.However the “DOCUMENT_TICKET_TEMP_PATH” cannot be updated from this screen, so I had to do go through “Reconfigure” through the installer on the App Server. I was certain I had already done this on our cloned instance, but anyway the “DOCUMENT_TICKET_TEMP_PATH” setting under Document Default Values now correctly matches the physical location on the App Server.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
