Calendar "Unexpected Error"
-
2007. augusztus 30. 2:35
Hi after deploying MS CRM 3.0. I get an "Unexpected Error An error has occurred. For more information, contact your system administrator. " when ever a calendar function is selected.
All other functions appear to work.
Have I missed a step in the implementation guide?
Any thoughts on how to recify this problem?
Setup:
1x 2003 Server, AD, exchange.
1x 2003 Server, SQL, CRM
Thanks for any help
Mark
Az összes válasz
-
2007. augusztus 30. 7:56
Mark,
Is there anything in the event log when you get this error. As a long shot have you checked that the website and mscrmservices in IIS have an asp.net version of 1.1 and not 2?
Alex
-
2007. augusztus 31. 2:30Thanks Alex.
You are right it is running asp.net 2.0.
I tired to install asp.net1.1 but system says it is already installed but in "programs installed" it is not listed.
So hunting on how to install asp.net1.1 in this scenario. -
2007. augusztus 31. 8:25
Mark,
Check the you have %windir%\Microsoft.NET\Framework\v1.1.4322.
If you do then re-register it using aspnet_regiis.exe; do aspnet_regiis.exe -? from the above directory for more info.
Alex
-
2007. szeptember 19. 20:51Hi,
Did this fix work for you? I have the exact same issue. I did try as suggested to switch the ASP.Net to version 1.1 in the IIS but the only thing this did do for me is to make CRM completly non responsive. Did you get this issue resolved at all?
Could you share the exact steps you took to get this resolved?
Thank you for the assiatance,
Thomas -
2007. szeptember 19. 21:21Hi,
We resolved the issue. Thank you for trying to assist.
Best wishes,
thom -
2007. szeptember 25. 14:23
Hi,
I have the same problem, could you share the resolution please.
-
2007. szeptember 28. 0:08Hi All thanks for your replies.
My resolution to this problem (was probably a bit dirty but as it was a new install on a new server build):-
1. Remove ASP.net 2.0.
2. Under IIS configuration change CRM services to ASP.net 1.0
3. install ASP.net 2.0
4. Change CRM Reporting services to ASP.net 2.0
Since these changes everything has been working fine with no problems detected.
Mark