-
Notifications
You must be signed in to change notification settings - Fork 11
Troubleshooting
NEW - Get help from the MA from the PSMA AI Assistent
I want to emphasize that this is a free product, and as such, no free support is offered. For general questions, please post them in the FIM 2010 forums, where helpful individuals (including myself occasionally) are available to assist.
If you wish to purchase this Management Agent with support, please contact me at soren@granfeldt.dk for pricing and details. Additionally, if you encounter any issues or have useful scripts for the MA, feel free to send them to soren@granfeldt.dk or leave them in the comments, and I will make them available for public download. However, please do not use this email for support inquiries, as direct support is not available without a purchase.
Your contributions can help enhance the quality and reach of this Management Agent. Below, you’ll find tips and tricks shared by the community and users of this MA.
The MA uses extensive tracing throughout the code. You can get at this information in different manners. So, when configuring and creating/testing script, you can use a tool like DebugView to catch tracing information from this MA.
Ensure 'Capture Global Win32' is enabled in the Capture menu. For a more readable tracelog in DebugView, remove the tick mark at "Force Carriage Returns" under Options in DebugView.
Other errors and warnings that are not caught by the MA and the logging mechanics can be found in the Application Event Log on your Synchronization Server.
As of version 5.5.1.1017, you can now use Write-Debug, Write-Verbose, Write-Progress, Write-Warning and Write-Error in your scripts. Information from these lines is picked up and send to the trace log.
To make sure that output from Write-Verbose and similar, you should set the corresponding preference to 'Continue' in the start of your scripts, i.e.
$VerbosePreference = 'Continue'A few reports have mentioned that no specific error is reported, if your server does not have PowerShell 3.0 or later installed. The requirement for PowerShell version 3 is mentioned in the requirements section, however, it is repeated here as this is a common mistake. You can find PowerShell 3 downloads here.
As of build 5.5.3508, you need to create an eventlog source called "PowerShell Management Agent". The PSMA will try to create this, but if enough permissions are not available, you will get this error. This is easiest done by using the PowerShell command below -
New-EventLog -Source "PowerShell Management Agent" -LogName ApplicationYou can send PSMA script output as Events to the Windows Event Log. See this example for more information.
Make sure that the FIM Synchronization Service service account is able to execute script on the FIM server. A hint for doing this is trying to start a PowerShell prompt using RunAs as the service account and make sure that the PowerShell scripts can be executed as that user / in that security context. Also, verify that the PowerShell Script Execution Policy has been configured correctly (see more about using the Set-ExecutionPolicy Cmdlet here)
Since the Management Agent is a DLL download from the internet, it may become blocked (Blocked File Protection Control). You can read more about this and how to unblock it here.
If the Management Agent is unable to properly interpret the schema file, it displays this error -
Unable to retrieve schema. Error: An anchor attribute defined by the extension must not be of type Reference or Boolean. A multivalued attribute defined by the extension must not be of type Boolean.
This might be a bit confusing. However, often times this is because no anchor is defined. Please see schema section for more information on how to schema script with proper object types.
This error may also occur if the service account can't execute the schema script (see Execution Policy problem)
This error may also occur if the path to the schema script contains spaces. The current version does not support spaces in path names. Use short pathname or place scripts in folder path without spaces.
When returning attributes from your scripts, please note that the FIM Schema in some cases is case-sensitive; this means that returning an attributename as "samaccountname" is not the same as returning "sAMAccountName". As a general rule, you should use the same casing for all attributenames as you have specified in the schema script. Please note that this is a requirement for the FIM Synchronization Engine, not from the PSMA.