1

I have a Sharepoint 2013 Server in our DMZ (non-Domain joined). We published it to the Internet (with local User Accounts) and now we want to login with our Active Directory Accounts from our Domain.

The best way I found to perform this, is to do an Active Directory Import. I opened the Ports 443, 25, 389, 88 and 53 to our Domain controller (to execute the AD Import).

Now I filled in all needed information and I can see all our AD containers. When I want to continue, the following Error displays: NeedsFullImport

NeedsFullImport Error

My Logfiles shows the following:

The Execute method of job definition Microsoft.Office.Server.UserProfiles.ADImport.UserProfileADImportJob (ID 2d42d33c-8eb1-471c-bfc6-4c82e6fd27fb) threw an exception. More information is included below.

NeedsFullImport

I found 2 posts on the Internet, but no one had a solution to this problem. Please guys, help me if you can I'm already really desperate.

  • Have you tried to use the LDAPS port 636? Usually you want a secure connection going into DMZ with all of your accounts... – Benny Skogberg Sep 21 '16 at 10:44
  • 2
    The User Profile Service has nothing to do with logging onto SharePoint (Authentication or Authorisation). In order to be able to log onto this farm with credentials from your domain, you'll have to either set up SAML auth via ADFS or if you wish to use Windows Authentication (NTLM or Kerberos), you will need your SharePoint's (non-existant) domain trust the domain who's accounts you wish to log in with. Keep in mind that your SharePoint environment is in an unsupported configuration as local accounts (and non-domain-joined servers) is not supported for production scenarios. – Greg W Sep 21 '16 at 12:11
  • Edit: Forgot Forms-based Auth. which is also a possibility though I've never set it up. – Greg W Sep 21 '16 at 12:56
  • First of all, thx for the responds. @Benny Skogberg: I opened the Port 636 to the Domain Controller as well, but it didn't work out. When I pressed Populate Containers, the Error "The LDAP server is unavailable" showed up. I didn't had the problem with the port 389. – IT.Guy Sep 21 '16 at 13:44
  • @Greg W: We already got a Oneway-Trust to our DMZ and opened the ports to the domain controller as well. After I press populate containers, I can cearly see the traffic over this port on the firewall. I think that the trust should be alright, but the error occurs for an other reason. Maybe someone knows why? – IT.Guy Sep 21 '16 at 13:50
0

Solution: I found these Errors in the Sharepoint Logs, that the databases from Sharepoint needed to be upgraded. I found Powershell commands to fix this Problem:

(To be able to upgrade the databases:)

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

(To upgrade all needed Databases:)

Get-SPContentDatabase | ?{$_.NeedsUpgrade -eq $true} | Upgrade-SPContentDatabase

(One Database woudn't work so I had to upgrade manually:)

(Get-SPDatabase | ?{$_.type -eq "Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase"}).Provision()

That's it, after this I could create a new data import. I just wanted to share it with you guys, maybe someone of you get the same problem.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.