-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SharePoint Sync.psm1 Line 121 and later fails. #9
Comments
It is not a issue.. I thought the PowerShell script simply upload the XML but it actually updated the XML to new values and then uploads. |
Thanks for testing and filing the issue. I'm interested in the error as I didn't see that in my testing. Can you describe your environment for me? |
Environment is AD, SQL, WFE and App Server and MIM is installed on App server. first time I ran the script, then deleted the configurations from Sync tool, then executed the script again and got the errors as script line refers above does not have litware and inc referenced any more. I was not sure if my local xml files were updated. Don't you think it is good a copy of the original and then modify them before uploading. This way the basic template will always be there for next run. |
Ah, that makes sense. I'll file that as a new issue. |
$domainPartition = Select-Xml -Xml $admaXml -XPath "//ma-partition-data/partition[name='DC=Litware,DC=com']"
VERBOSE: Contacting AD to get the partition details
VERBOSE: Configuring the Active Directory Connector
VERBOSE: AD Forest: contoso.local
VERBOSE: AD OU: ou=users,dc=contoso,dc=local
VERBOSE: AD Credential: contoso\contosoadmin
VERBOSE: AD Naming Partition: DC=contoso,DC=local
VERBOSE: AD Config Partition: CN=Configuration,DC=contoso,DC=local
The property 'name' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:122 char:5
The property 'dn' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:123 char:5
The property 'name' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:124 char:5
The property 'guid' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:125 char:5
The property 'inclusion' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:126 char:5
The property 'exclusion' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:127 char:5
The property 'inclusion' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:128 char:5
The property 'name' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:132 char:5
The property 'dn' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:133 char:5
The property 'name' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:134 char:5
The property 'guid' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:135 char:5
The property 'inclusion' cannot be found on this object. Verify that the property exists and can be set.
At F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\SharePointSync.psm1:136 char:5
VERBOSE: Importing the Synchronization Service configuration
VERBOSE: Path: F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync
VERBOSE: Performing the operation "The MIIS Agents and Metaverse Schema will be replaced with the sever import files in F:\SP20
16\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync." on target "MIIS Service".
VERBOSE: Metaverse schema updated.
VERBOSE: Metaverse schema updated.
VERBOSE: Management Agent Created: F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\MA-ADMA.XML.
VERBOSE: Management Agent Created: F:\SP2016\PnP-Tools-master\PnP-Tools-master\Solutions\UserProfile.MIMSync\MA-SPMA.XML.
VERBOSE: Metaverse Schema Updated With IAF and Metaverse Deletion Rules.
WARNING: =======================================================================================
WARNING: IMPORTANT: the Password must be set on the AD Connector before sychronization will work
WARNING: =======================================================================================
VERBOSE: Configuring the SharePoint Connector
VERBOSE: SharePoint URL: http://sps-app-0:2016/
VERBOSE: SharePoint Host: sps-app-0
The text was updated successfully, but these errors were encountered: