FIM Password Reset Client Broken - Error Code: 40007 RRS feed

  • Question

  • I've got a handful of machines that are getting a pop-up error message immediately upon login to to their workstations in reference to the FIM client software installed on the machine.  The error is as follows:

    "FIM Password Reset Registration

    An error has occurred. Please contact your helpdesk or system administrator for assistance. Error Code: 40007"

    We've tried uninstalling and reinstalling the client but that did not fix the issue.  I've seen similar problems reference this error where the machine was external to the network and it required the FIM Portal URLs be added to the Trusted Site or Intranet Sites in IE, but this is on the internal network and on the domain.  I did, however, go ahead and add the URLs anyways just to see if it might fix the problem regardless.  It did not.  If the user clicks on the link at the login screen (forgot your password) then they will also immediately get this error message and will be unable to go any further through the reset process.

    Any ideas on something I could check to fix this?

    The client in question is running Windows 7 Pro 32bit, IE 8, FIM client version 4.1.3461.0

    There are only a handful of machines that have this problem.  There are hundreds more that are not showing this problem with the same configurations.

    Friday, November 15, 2013 5:13 PM

All replies

  • You probably want to start with the client side trace and see anything special comes up.

    The FIM Password Reset Blog

    Monday, November 18, 2013 11:43 AM
  • I did get a few errors while running the trace.  I believe this is the pertinent information, but I can post the entire error if need's just a little wordy and I didn't want to muddy the waters.

    "System.Xml: System.UnauthorizedAccessException: Access to the temp directory is denied.  Identity '<domain>\<username>' under which XmlSerializer is running does not have sufficient permission to access the temp directory.  CodeDom will use the user account the process is using to do the compilation, so if the user doesnt have access to system temp directory, you will not be able to compile.  Use Path.GetTempPath() API to find out the temp directory location."

    Any idea what temp directory I should be looking at?  I assume I just need to find out and check the permissions on that guy.

    Tuesday, November 19, 2013 3:15 PM
  • Did fixing the permissions on this folder resolve the issue?

    Russell Lema

    Wednesday, July 8, 2015 3:10 PM