Another Appfabric installation error due to PSModulePath

Error:

Product: AppFabric 1.1 for Windows Server -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action Env_PSModulePath_powershell_i, location: C:\Program Files\AppFabric 1.1 for Windows Server\Microsoft.ApplicationServer.InstallHelper.exe, command: powershell.exe "-command \"$str = [System.Environment]::GetEnvironmentVariable(\\\"PSModulePath\\\",[System.EnvironmentVariableTarget]::Machine); $str = $str+\\\";C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\\\"; C:\Windows\system32\setx.exe /MPSModulePath \\\"$str\\\"\"" "C:\Users\senthil\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2014-09-28 20-02-35).log"

 (Or)
Unable to proceed the installation after restarting the Server by AppFabric.

Reason:

You will this error during the installation of Appfabric service in SharePoint server 2013. You need to fix 2 issues. 

1. Need to update the "PSModulePath" in the environment variable section
2. Enable the "Windows Firewall" service

Solution:

1. "PSModulePath" in the Environment variable will have extra double quote (") at end of the value. Appfabric installation will not be able to parse the value, if it contains the double quote. So we need to remove that additional character.   Follow the below screenshots to remove the extra double quote character

2. One more important thing is, we need to enable to the "Windows firewall" service which is mandatory for Appfabric to complete its full installation. Because

Appfabric will try to add few entries in the Windows firewall.  See the below screenshot for more info.

(This second one has killed me a lot)

How to: Shrink the SQL Server 2008 Log file (Even though in Mirroring)

How to: Shrink the SQL Server 2008 Log file Even though the database is in Mirroring


Sometimes you will not be able to shrink the SharePoint database log files, if the SQL Server 2008 database is in Mirroring option.


Solution:
At that time you need to open the "SQL Server management studio" and run the below query.



USE [WSS_Content_DBName]
Go
BACKUP LOG [WSS_Content_DBName] TO DISK='NULL'
Go
DBCC shrinkfile ('WSS_Content_LogName', 1) 
Go


Update:
If the above lines are not working, just try again the same query. Because sometimes it will take few more seconds to shrink the log files.

Issue: Multiple login prompts while browsing a SharePoint application

Issue:

Sometimes, you will be prompted to type the Login credentials to enter into the SharePoint application.

(Amazingly, this will not occur in Firefox)

Reason:

Because, all your browser requests may be processed through the proxy. So the response will be passed through the proxy and the converted HTML output will be displayed in browser. So, the browser will trying to access the SharePoint application's resources (like images, css) directly through the HTTP. By default, nobody can access the SharePoint resources directly in the browser and they can be accessed only if he is the authorized person.

I meant, this kind of access is equivalent to access a image directly from SharePoint image library in browser like, http://sensoft2000-sharepoint.blogspot.com/Images/Logo.jpg (Just an example).

Solution:

You have to add the URL in trusted sites zone of the IE and the URL should be added in exception list. 


Just follow the below mentioned steps to fix this issue.

• Open the IE browser
• Go to Tools and click internet options
• Then Click "Security" tab
• Select "Trusted Sites"
• Click "Sites" button
• Type your URL in the text box and click "Add" button.
• Click "Close" button
• Click "Apply" button
• Go to "Connections" tab
• Click "LAN Settings" button
• Here your "Proxy Server" check box may be checked already.If not, Select it
• Click "Advanced" button
• Now, you will see a Text area in the "Exceptions" panel.
• Here you have to add your URL. for example, if your URL is like http://moss.sensoft2000.com (example), then you need to add the URL as mentioned in the below screenshot *.sensoft2000.com. 

Thats it...

Error: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

Error:


The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317) 


Reason:
1. Security context of your session may be expired.
2. You/somebody may have changed the date/time in the server.


Solution:
1. Just change/update the Date/Time in the SharePoint server.
2. Increase the Security context in SharePoint central admin. This can be done by following the below steps:

• Go to central admin
• Go to  "Application management section"
• Go to "Web Application General Settings"
• Go to "Web page Security validation" section & increase the timeout field. Or, you can simply disable this option.

Thats it...

Error: CREATE TABLE permission denied in database . at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

Error:
CREATE TABLE permission denied in database . at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

Reason:

You will get this error, when you are trying to create a new SharePoint web application using the ATTACHED DATABASE through the central admin. Because, your central admin user (that is current user to create a website) may not having a permission to create tables dynamically in the SQL Server. 

Solution:

Solution is very simple. Just attach the database in SQL Server using the current user of the central admin as the owner of the DB. (But it takes long time for me to find out the exact reason).

For example, If your current central admin logged-in username is "domain\senthil" (Assumes, senthil is going to create a new web application) , then you should attach the database using the "domain\senthil" username.

You can change the owner of the database during the "Attach databases" as per the below screenshot.

Thats It...

The specified SPContentDatabase Name=WSS_Content Parent=SPDatabaseServiceInstance Name=MSSQL2008 has been upgraded to a newer version of SharePoint.

Error:

The specified SPContentDatabase Name=WSS_Content Parent=SPDatabaseServiceInstance Name=MSSQL2008 has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

Reason:

This error may occur, if you are trying to attach the SQL server 2008 "MDF" file in SQL Server 2008 (No typo :) ) and the SharePoint Version is MOSS 2007 with no service packs.

Solution:

Just install the WSS service pack 2 & MOSS service pack 2. Now, you can attach the database without any issue.

For more info, refer my another post here

Thats it...

Failed to instantiate file "TopAnswer.webpart" from module

Error:

Failed to instantiate file "TopAnswer.webpart" from module "WebPartPopulation": Source path "dwp\TopAnswer.webpart" not found. Troubleshoot issues with Windows SharePoint Services.

Solution:

This error will occur, if you applied only the WSS 3.0 SP2. You may not installed Office Server SP2.

I wrote a simple solution in another post. Just go through the url and install Office Server SP2.

http://sensoft2000-sharepoint.blogspot.com/2009/07/moss-2007-database-attach-error.html

MOSS 2007 Database Attach Error

Error:
The specified SPContentDatabase Name=WSScontent_2009 Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object

Solution:

Dont get confused with other solutions. Just install Moss 2007 SP2. Thats it.

Google about "wssv3sp2-kb953338-x86-fullfile-en-us.exe" and install this service pack first. And then install "officeserver2007sp2-kb953334-x86-fullfile-en-us.exe"

Sometimes you will get error during the Office Server SP2 (Not WSS 3.0 SP2). At that time, try to extract the MOSS SP2 in some other location and then execute the .msp file from the newly extracted folder.

Command to extract the exe: 

officeserver2007sp2-kb953334-x86-fullfile-en-us.exe /extract:"c:\mosstemp\"

Once the files are extracted, execute the "coreserverwwsp2.msp" file.

Thats it...