When i try to configure Powershell MA on a Windows 2008 with FIM 2010R2 I get the following error :

Unable to retrive schema: Error: An anchor attribute defined by the extension must not be of type Reference or Boolean. A multivalued value defined by the extension must not be of type Boolean.

And the following eventlog message:

The extensible extension returned an unsupported error.
The stack trace is:
"Microsoft.MetadirectoryServices.ExtensionException: The Schema returned from the PowerShell compliant server is null
  at Microsoft.IdentityManagement.Connector.PowerShell.Bridge.ConfigBridge.GetSchema()
  Forefront Identity Manager 4.1.3508.0"

I have another posts about configure MS PowerShell MA http://social.technet.microsoft.com/Forums/en-US/54bb4846-4de8-4128-b8bb-adfe50d16c6f/fim2010r2-powershell-connector-create-new-ma-gives-error-emmsschemaclassnotfound?forum=ilm2on a Windows 2012 server where i got the same error if i didn't created the Powershell folder under extensions folder and placed the FIMPowerShellConnectorModule.psm1 module there. After this i got Another error also about schema not found. Not sure if these two is connected or not.

But when i tried to do the installation and configuration on Another lab server "Win2008" i got stuck on the first error and on this server it didn't help to create the powershell folder.

I could also see that it's not even run the GetSchema cmdlet, and this is the trace file generated from config

ConnectorsLog Verbose: 0 : Method Name : PowerShellConnector : .ctor
Initiated PowerShellConnector Constructor
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : .ctor
Initiated BridgeBase constructor
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : .ctor
Initiated ConfigParametersParser constructor
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : ParseConfigParams
Initiated the Parsing of the Configuration Parameters
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : ParseConnectivityParams
Initiated the Parsing of the Connectivity Page Parameters
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : ParseConnectivityParams
Parsing of the Connectivity Page Parameters completed
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : SetPSCredential
Constructing PowerShell credential object
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : SetPSCredential
Constructing PSCredential for user: lumaville\administrator
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : ParseConfigParams
Construction of the PowerShell credential object completed
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : ParseConfigParams
LogonType selected is None, ImpersonateConnectorAccount is False, LoadUserProfileWhenImpersonating is False
ConnectorsLog Verbose: 0 : Method Name : ConfigParametersParser : ParseConfigParams
Parsing of the Configuration Parameters completed
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : IntializeContext
Initializing the PowerShell context with the following PowerShell credentials
ConnectorsLog Verbose: 0 : Method Name : PowerShellContext : IsScriptSigned
Script signed is False
ConnectorsLog Verbose: 0 : Method Name : PowerShellConnector : GetSchema
IntializeContext completed
ConnectorsLog Verbose: 0 : Method Name : PowerShellConnector : GetSchema
Initiated ConfigBridge constructor
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : GeneratePSContentScript
Generating the temporary file path for the PowerShell script
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : GeneratePSContentScript
Creating a file in the following temporary file path C:\Windows\TEMP\FIMPowerShellConnectorModule.psm1
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : GeneratePSContentScript
The temporary file path for the PowerShell script created
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : GeneratePSContentScript
Generating the temporary file path for the PowerShell script
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : GeneratePSContentScript
Creating a file in the following temporary file path C:\Windows\TEMP\ss2xvrzw.ps1
ConnectorsLog Verbose: 0 : Method Name : BridgeBase : GeneratePSContentScript
The temporary file path for the PowerShell script created
ConnectorsLog Information: 1 : Method Name : ConfigBridge : GetSchema
Initiated GetSchema method
ConnectorsLog Verbose: 0 : Method Name : ParameterBuilder : .ctor
Initiated ParameterBuilder Constructor
ConnectorsLog Verbose: 0 : Method Name : ParameterBuilder : GetConfigCommandParameters
Fetching the configuration command parameters
ConnectorsLog Verbose: 0 : Method Name : ParameterBuilder : GetConfigCommandParameters
Script type : Schema
ConnectorsLog Verbose: 0 : Method Name : ParameterBuilder : GetConfigCommandParameters
GetConfigCommandParameters completed
ConnectorsLog Verbose: 0 : Method Name : ConfigBridge : GetSchema
Executing the Schema script present at the following path C:\Windows\TEMP\ss2xvrzw.ps1
ConnectorsLog Verbose: 0 : Method Name : PowerShellRuntime : InvokePowerShell
Invoke PowerShell to execute the PowerShell commands and get the output as PowerShell Object collection
ConnectorsLog Verbose: 0 : Method Name : PowerShellRuntime : Initialize
Creating a new PowerShell instance
ConnectorsLog Verbose: 0 : Method Name : PowerShellRuntime : Initialize
Creation of new PowerShell instance completed
ConnectorsLog Information: 1 : Method Name : PowerShellRun

On Wed, 26 Mar 2014 15:00:20 +0000, Ulf Lindström wrote:

When i try to configure Powershell MA on a Windows 2008 with FIM 2010R2 I get the following error :

You don't mention SP1 in the above. What version of FIM 2010 R2 are you at
exactly? According to the documentation you need to be at least running:

FIM 2010 R2 SP1 hotfix 4.1.3441 - KB 2

The extensible extension returned an unsupported error.
The stack trace is:
"Microsoft.MetadirectoryServices.ExtensionException: The Schema returned from the PowerShell compliant server is null
  at Microsoft.IdentityManagement.Connector.PowerShell.Bridge.ConfigBridge.GetSchema()
  Forefront Identity Manager 4.1.3508.0"

And yes it's running FIM201R2 SP1 in both Environments i have tested to just to apply "FIM 2010 R2 SP1 hotfix 4.1.3441 or better (KB 2832389)" and the latest "4.1.3508.0" i think but no difference. And i have added synk account to administrators Group just in case of permission issue.

I can confirm I am having the same issue.

Hotfix patched my SP1 Install to version 4.1.3508.0

I copied the scripts from this post: http://social.technet.microsoft.com/wiki/contents/articles/23925.office365-cloud-group-membership-management-with-windows-powershell-connector-for-fim-2010-r2.aspx

and I get the following error in the Application Event Log:

The extensible extension returned an unsupported error.
 The stack trace is:
 
 "Microsoft.MetadirectoryServices.ExtensionException: The Schema returned from the PowerShell compliant server is null
   at Microsoft.IdentityManagement.Connector.PowerShell.Bridge.ConfigBridge.GetSchema()
Forefront Identity Manager 4.1.3508.0"

Any updates on this one? I am having the same issues.

Hello,

Same issue with the version 4.1.3510.0.

Any updates ?

Hello - 

Issue seem to appear with version 4.1.3559.0 as well. 

 "Microsoft.MetadirectoryServices.ExtensionException: The Schema returned from the PowerShell compliant server is null
   at Microsoft.IdentityManagement.Connector.PowerShell.Bridge.ConfigBridge.GetSchema()
Forefront Identity Manager 4.1.3559.0"

Any resolution on this?

Does anyone have any answers about this?  Also, where the heck do I find FIMPowerShellConnectorModule.psm1?

I am replying to this post very late but might be helpful :)

Use "System.Management.Automation.PSCredential" instead of PSCredential so that your schema discovery parameter would looks like :-

param( 
[System.Collections.ObjectModel.KeyedCollection[[string], [Microsoft.MetadirectoryServices.ConfigParameter]]]  
    $ConfigParameters,
    [System.Management.Automation.PSCredential]
    $PSCredential
)

Your powershell MA will discover schema now.

It's not too late for me.  :-) I'm still struggling to get this sample to work.

Could you possibly post the entire schema script that you're using?

Also, do you have any tips on debugging this code?  I have no idea where or how to write debug output so I can see what's going on or how far the script has run.

Any help would be greatly appreciated.

I think I solved my own problem.  

After some debugging, it seems there was a bug in the AD Sync PS Connector Module sample.  There was a missing close bracket.

I found the problem by writing event log entries  in lieu of throwing errors since it seems that whenever something fails in the scripts, the only thing that makes it to the event log is a generic error about a null schema.

I made a correction the the script so hopefully it should work now.