Hi,Part of theSCSM beta FIM wil be required for providing the Password Reset function. First of allI'am quite new into FIM. I've configured a FIM server (http://technet.microsoft.com/en-us/library/ee534909(WS.10).aspx)on a single box including SQL, WSS, FIM Service and Portal andSynchronization Service.When I try toopenhttps://localhost/identitymanagementthe following message is displayed: An error occurred during the processing of. The resource object with key 'javaScriptDisabledErrorText' was not found. OPening https://localhost/passwordportalresultst in: An error occurred during the processing of. The resource object with key 'default_title' was not found.At this point unfortunately I stuck.Regards, Ronny de Jong

looks like the sharepoint solution is corrupted. would running a repair of the "FIM Service and Portal" help?The FIM Password Reset Blog http://blogs.technet.com/aho/

Didnt mean to point the obvious but looking at the error message token it seems like JavaScript is disabled on your browser. Have you checked that already? Thanks & Regards, Jameel Syed Principal Consultant, fimGuru - Your window into simplified identities jameel.syed@fimguru.com - http://www.fimguru.com

Hi,Part of theSCSM beta FIM wil be required for providing the Password Reset function. First of allI'am quite new into FIM. I've configured a FIM server (http://technet.microsoft.com/en-us/library/ee534909(WS.10).aspx)on a single box including SQL, WSS, FIM Service and Portal andSynchronization Service.When I try toopenhttps://localhost/identitymanagementthe following message is displayed: An error occurred during the processing of. The resource object with key 'javaScriptDisabledErrorText' was not found. OPening https://localhost/passwordportalresultst in: An error occurred during the processing of. The resource object with key 'default_title' was not found.At this point unfortunately I stuck.Regards, Ronny de Jong Hi Ronny,I'm getting the same JavaScripDisabledErrorText message, but only on the second node of my WSS farm.I'll be troubleshooting this week and will update this thread on what I find. Can you confirm the following: Can you open the root (http://localhost) site collection successfully? In your SharePoint logs directory (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS), scan your most recent log for any errors relating to Resources.*.resx. I see errors for Resources.en-US.resx which may or may not be related. Oh, the javascript error doesn't seem to be browser or server related, I think the issue runs deeper than that as I can open the portal on my other node successfully from the same browser.Thanks, Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

Hi Anthony,Nice blog btw - where you have been!? :)I'm seeing the same issue but only on the second node of my WSS farm and I've completely ripped out SharePoint and reinstalled with the same results. It certainly smells like a bad SP install given the additional errors I'm seeing (which relate to the WSS three-state workflow which I actually have disabled) but I haven't found much on how to resolve it.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

No, doesn't seem to be browser related - I can hit the portal on a different node without difficulty so it's not the browser. Smells like something at the SharePoint layer.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

btw, afaik, we don't support Sharepoint FarmThe FIM Password Reset Blog http://blogs.technet.com/aho/

btw, afaik, we don't support Sharepoint Farm The FIM Password Reset Blog http://blogs.technet.com/aho/ According to Andreas and Darryl you do:https://connect.microsoft.com/site433/feedback/ViewFeedback.aspx?FeedbackID=519596Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

In your SharePoint logs directory (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS), scan your most recent log for any errors relating to Resources.*.resx. I see errors for Resources.en-US.resx which may or may not be related. Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com Applying SP2 for WSS 3.0 resolved this error for me but not the javascript error so this was not related.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

Thanks for your answering Brad,In meantime we've installed FIM from scratch including WSS. I've to verify if it's solved now. Based on your findings...fingers crossed :-)I'll provide you feedback as proposed.Regards,Ronny Ronny de Jong - Senior Engineer - Manageability

Hi, I am also having this issue after reinstalling FIM 2010 for the second time (first was test deployment). Followed the exact same process as the first time when everything worked fine. What was the fix? J

... restored VM from post-prereq snapshot, uninstalled and reinstalled sharepoint then completed the FIM install again following the exact same process, and this time everything works fine.. One thing i noticed, is that the time it did not work, I did not get the screen to set up/show the local security groups that are created during the Portal installation. J

Hi J, our experience is the same. Complete install from scratch (WSS/FIM) solved the issue. I doesn't like this way of debugging, buth due to timeconstrains I've too!Ronny de Jong - Senior Engineer - Manageability

Hit the same exact error.Uninstall/Reinstall of just the Portal feature solved it for me. Didn't touch the Service or WSS.CraigMartin Edgile, Inc. http://identitytrench.com

Part of the problem seems to stem from how long it takes the SharePoint WSP solution files to replicate throughout the WSS Farm. The default timeout is insuffcient and so you need to specify a different timeout when installing the Service and Portal.msi.msiexec /i "service and portal.msi" SHAREPOINTTIMEOUT=300Even with this timeout I still encounter attempts where one of the solutions fails to deploy causing the entire installation to roll back.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

It happened to 2nd service/portal server with WSS farm mode. From 1st service/portal server, remove Portal feature only from 'Change' option of Programs and Features in Control panel. And add back the Portal feature from the same 'Change' option solved the error and Portal site was available to access from the 2nd server as well.-Henry Min