I installed the SharePoint 2013 prerequisites and it could not continue on AppFabric. 1.1. See this link for the solutions.
In my case, here is the solution I applied:
- Go to My Computer, right-click Properties
- On the System page, click Advanced System Settings on the left-side pane.
- If you receive a UAC prompt, click on Yes to launch the System Properties dialog box
- From the Advanced tab, click Environment Variables
- Within the System Variables section in the lower half, select PSModulePath and click on Edit (or double-click PSModulePath)
- Append the following path to PSModulePath entry in the environment variables
C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules
- Ensure that the PSModulePath entry looks like this:
C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules
The population wizard in IBM Connections enables the user to automatically populate the PEOPLEDB database with the required information from the LDAP. The information from LDAP such as user’s personal information are then displayed in the user’s profile in IBM Connections.
- IBM Connections 4.0 CR4
- DB2 9.7
- Domino 8.5.3
The wizard fails when I assign a value in the Country field in Domino.
Solution I applied:
In Domino, I changed Philippines to ph. Connections validates this as country code; therefore, the entire word is invalid.
The wizard fails because of telephone number (Office number).
Solution I applied:
Make sure that the character length of the value in Office number does not exceed 32.
Password expiry can be prevented; however, since this is a server, it is expected to be secured always since it is also expected to contain sensitive information. Check out this link to change the password expiration settings.
Please take note that if you are using an image backup, you cannot change these settings.
When I try to look up for people and/or groups from Active Directory, an error with a red font color shows saying “Sorry, we’re having trouble reaching the server.“
To fix this, you must have an access to the Central Administration site.
- Go to Application Management > Web Applications > Configure alternate access mappings.
- Click Add Internal URLs.
- Choose a web application where you want to apply the setting from the Alternate Access Mapping Collection button.
- Type a valid URL protocol, host and port. For example, http://192.168.0.21. In my case, this is the IP address of my Active Directory, where my users and groups are pulled from.
- Click Save.
- Optional: Restart the web application from the IIS Manager, if you cannot wait for it to take effect.
- The error should be gone by now, if done correctly.