Project Server 2010, IE Ver.: 8.0.7600.16385, Trying to go to Timesheet or Repair Timesheet pages and getting a blank page and the error 'Error de página' (left down corner).
-
16 Agustus 2011 10:21
Hi,
I'm using Project Server 2010, and recently around 25 users have renovated their computer, and it is growing because more people will get new coputers, the Operating System is Windows 7 Enterprise 64 bits, and the Internet Explorer version is 8.0.7600.16385.
The new computers are made from the same image, so all of them have the same version of everything.
Up to now (before they changed their computer), or even in my case, I'm using Windows 7 Enterprise 32 bits, and IE 9.0.8112.16421, there was no problem, but for these new computers when they try to diplay the Timesheet or the Repair Timesheet pages they get a blank screen with the error 'Error de página' (downside left corner).
The only way for them to be able to go to those pages is going to Herramientas --> Opciones de Internet --> Opciones Avanzadas --> Restablecer (Translated: Tools-->Internet options-->Advanced Options-->Reset) , and then it works, but just for a while, probably the next day it won't work and they will need to do this workaround again.
The workaround is not a good solution because every time they loose some information like pages and so on...
Do you know how to solve this issue?
Thank you and regards,
José Espases
Semua Balasan
-
03 Oktober 2011 14:12Moderator
Jose:
I'm sorry that nobody replied to your question. I'm closing the thread for now. Please re-post if you need to pursue this further.
Gary Chefetz, MCITP, MCP, MVP msProjectExperts
Project and Project ServerFAQs
Project Server Help BLOG- Ditandai sebagai Jawaban oleh Gary Chefetz, MCITP, MCT, MVPModerator 03 Oktober 2011 14:12
- Tanda sebagai Jawaban dihapus oleh José Espases 07 Mei 2012 8:50
-
07 Mei 2012 8:50
Hi,
After some months I've found where the problem was:
There was an script that was applying the value of '0' to the parameter 'Use HTTP 1.1', so it was Unchecking this parameter:
Just changing the script and making it to put the 'Check' value (1), the problem was solved.
It has been needed to open an Incidence with Microsoft to solve this issue.
Regards,
José Espases
- Ditandai sebagai Jawaban oleh José Espases 07 Mei 2012 8:50