My company is having an issue. At the moment, we are testing APPS10 with an expected go live date in November. Since testing, with a very limited set of users, we have noticed that some are getting .dll errors for pages they frequent. One day during testing they can see it, the next they can’t. In apps 9, the user could technically cause a .dll error if they cancel out of the download at the bottom when they first go to the page. In 10, there is no cancel button available when downloading the package to view the page (good improvement). We did some testing. While troubleshooting I moved the .dll file that the page was complaining about to a separate folder > went to “download all packages” > IFS realized it was missing 1 package and downloaded it > but we still can’t see the page until we delete everything out of the 2.0 folder. The only help I’ve gotten from IFS is to clear the cache which is essentially the equivalent of an uninstall/reinstall of the instance since it deletes the .exe file stored in that folder. We have an open ticket with IFS but so far, clearing the cache is their only solution. We’re worried that when we go live we’re going to have to remote into desktops constantly to mitigate this caching error and essentially, halt production in the process. We have very little people in our 10 testing environment and so far we’ve had about 15 users get the .dll error, some multiple times (and in multiple environments, 9 included) even after downloading all packages. Has anyone else experienced this when testing apps 10?
Best answer by AnnaView original