This problem can be solved in two ways.

Solution 1:

Follow the steps in this article: http://support.microsoft.com/kb/947215

This solution includes renaming of the registry keys which contain the profile information. If this solution does not work, try the following solution.

Solution 2:

The security rights on the ‘Default’ user folder must be corrected. Follow these steps:

1. Login with the local administrator account (if not possible, try to open a remote connection to the administrative share which contains the Users folder: \\computername\c$)
2. Navigate to your %systemdrive%\Users folder (commonly C:\Users).
3. Open the Properties of the folder and select Security.
4. Click Advanced.
5. Click Change Permissions.
6. Check Include inheritable permissions from this object’s parent and Replace all child object permissions with inheritable permissions from this object and click OK twice.

Security on the Default user folder is now properly set. Try to logon again.

So the Powershell script below won’t work for me and I decided to try it the old fashion way: cmd with icacls.

In no less then a hour I had a working script with just three effective lines. The cmd scripts first creates a list of user folders and puts them in a text file. Then each line from the text file is being read and by using icacls the ownership of each folder is changed to the appropriate user. The only condition is that your user folder name must be the same as the user account, which is usually the case with user folders such as home or profile folders.

CMD script:

@echo off

REM Create list of folders
dir /a:d /b X:\users >C:\temp\users.txt

REM Read each line from just created text file...
for /f "tokens=*" %%G in (C:\temp\users.txt) do (

REM ...and set ownership for each folder
icacls "X:\Users\%%G" /setowner "domainname\%%G"

echo.

)

Powershell script:

# Home drive folder
$homeDrivesDir="X:\Users"

# Your domain name
$domainName = "domainname"

#Save work directory
pushd .

# Location homedrive
set-location $homeDrivesDir

# For every folder in the $homeDrivesDir folder
foreach($homeFolder in (Get-ChildItem $homeDrivesDir | Where {$_.psIsContainer -eq $true})) {

 # Place ACL in a variable
 $Acl = (Get-Item $homeFolder).GetAccessControl("Access")

 Write-host "Settings rights for:" $homeFolder

 # Create the Access Rule
            $acct=New-Object System.Security.Principal.NTAccount($domainName,$homeFolder.name)

 Write-host "Owner of folder will be:"	$acct
 Write-host ""

 # Apply the access rule to the ACL
 $Acl.SetOwner($acct)
 Set-Acl $homeFolder.FullName $Acl
 Get-Acl $homeFolder.FullName  | Format-List

}

# Cleanup
popd

“Exception: The Active Directory user wasn’t found.”

This error occurs because there are server objects present from an earlier Exchange 2003 version. If there are no Exchange 2003 servers anymore in your organization, follow these steps:

1. Open ADSI Edit
2. Connect to the Configuration Naming Context
3. Navigate to CN=Your domain \ CN=Services \ CN=Microsoft Exchange \ CN=Your domain \ CN=Administrative Groups \ CN=Your Administrative Group \ CN=Servers
4. Delete this container only if it’s empty
5. Connection to your public folders with Exfolders should now work

Solution

In the TMG 2010 Tools & Software Development Kit you can find several useful tools. One of them is DNSToolsPack. You can find it here: http://www.microsoft.com/download/en/details.aspx?id=11183

1. Download the DNSToolsPack and extract the archive. It contains a .doc file, .rtf file and DNSTools.exe.

2. Copy the DNSTools.exe to the installation directory of ForeFront TMG (by default C:\Program Files\Microsoft Forefront Threat Management Gateway).

3. Open an command prompt (with an user account which has the appropriate rights for ForeFront TMG) and type in: dnstools /c which clears the DNS cache of TMG. Every new DNS request will now use the updated DNS entry.

There are several other commands available. Just type in dnstools to see what you might need.

“Do you want to view only the webpage content that was delivered securely?”

This problem can occur when HTTPS webpages use images, such as banners or product images from a HTTP site. The warning is shown because theoretically it would be possible the unsecured content can gain information from the protected (HTTPS) content. Using HTTP and HTTPS on the same page is known as ‘mixed content’.

However, if you know what you are doing this warning can be very, very annoying if it appears on every webpage you’re clicking. You can disable the warning by following the steps below:

Solution

1. Navigate to Tools > Internet Options
2. Open the Security tab
3. Select the Internet zone
4. Click on Custom level…
5. Under Miscellaneous, you can find Display mixed content
6. Select Enable
7. Click OK and click Yes if you receive the warning “Are you sure you want to change the settings for this zone?” and click OK again to close the Internet options windows.

All done now. You will not receive the warning again. If necessary, you can configure these setting for other zones too (like Local intranet or Trusted websites).

“It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.”

IIS 6.0 uses the process w3wp.exe. One or more application can run together in one ore more processes within the same application pool by ‘application pooling’, an isolation feature of IIS. Each pool has it’s own worker processes which handles requests. When you are using multiple versions of ASP.NET on your server, these processes will conflict with each other if using the same application pool. Therefore each ASP.NET version has to use it’s own application pool.

Solution

Open your IIS manager by using Start > Run > inetmgr

Open the Properties of your Virtual Directory by right-clicking it and check the Application pool being used under the tab Virtual Directory:

Now check the ASP.NET version being used under the tab ASP.NET:

Now make sure each Virtual Directory using the same ASP.NET version also uses the same application pool.

If necessary, create a new application pool in IIS Manager by right-clicking Application Pools > New > Application Pool…

This should do the trick!

IIS can listen on port 80 for multiple websites. If the given hostname corresponds with the configured binding in IIS, IIS will show the correct website. But SharePoint only listens on the hostnames which are configured within the alternate access mappings. Follow the steps below to configure the bindings in IIS and alternate access mappings within SharePoint.

Configure bindings IIS manager

1. Open the IIS manager (Start > Run > inetmgr)
2. In Sites, right-click the SharePoint site and click Edit Bindings…

3. Click on Edit…

4. Type the host name of the corresponding name in DNS.

Set alternate access mappings SharePoint

1. Open you SharePoint Central Administration site
2. On the main page, click Configure alternate access mappings

3. Click on Edit Public URLs or Add Internal URLs  if none are defined yet

4. Type the URL in the field Default. You could also fill in the other fields, like Internet or Extranet when your SharePoint site is published to the outside world.

Cause

This is by default a SharePoint security setting to prevent scripting or PDF attacks. The setting can be found in the Browser File Handling section which is set to Strict as default. If you do not have a problem with possible security risks, you can change the default behavior by following the steps below.

Solution

1. Open your SharePoint Central Administration site (http://servername:adminport/default.aspx) 2. Click on Manage web applications > Your SharePoint site name > Menu General settings > General settings > Section Browser File Handling
3. Change the setting Strict to Permissive and click OK

That’s it. PDF files can now be opened directly from your SharePoint site.

‘Exception occurred during event dispatching: java.lang.OutOfMemoryError: Java heap space’.

These errors are very clear and such an error indicates the application does not have enough memory assigned even if your machine has loads of memory. By default Java assigns 64 MB. Therefore you have to increase the assigned memory.

Solution

First you have to figure out which Java Runtime the application is using. In my case it’s Oracle Jinitiator version 1.3.1.22 which has it’s own Java environment. Or you are just using the regular Sun Java Runtime Environment, the standard edition which can be freely downloaded. Below you will find the methods to adjust memory size for either Java or Jinitiator.

Adjusting memory size Java

1. Navigate to your control panel and start the Java control panel or start C:\Program Files (x86)\Java\jre6\bin\javacpl.exe (64-bit) or C:\Program Files\Java\jre6\bin\javacpl.exe (32-bit).
2. Click on the tab Java and fill in the the desired memory values at start parameters, such as -Xms256M –Xmx1024M.

Xms = initial heap size (memory size at start of the application)
Xmx = maximum heap size (maximum memory size the application can use)

3. Click OK twice.
4. The settings are stored in ‘%userprofile%\AppData\LocalLow\Sun\Java\Deployment\deployment.properties’. If you want to push this settings to all of your users, you could use user Group Policy preferences to replace the file in the user directory with the new settings.

Adjusting memory size Jinitiator

1. Start C:\Windows\SysWOW64\plugincpl13122.cpl (64-bit) or C:\Windows\system32\plugincpl13122.cpl (32-bit) or navigate to your Control Panel and start it from there.
2. In the tab Basic at Java Runtime Parameters,  fill in the desired values like the image below:

Xms = initial heap size
Xmx = maximum heap size

I discovered the maximum heap size cannot be set at 1024M, this will crash the application. So I used 768M, which also must be enough memory space.

3. Click Apply.
4. Settings are stored in a file ‘properties13122’. It can be found in the folder ‘.jinit’ in the home folder or user profile of the user. If you want to push this settings to all of your users, you could use user Group Policy preferences to replace the file in the user directory with the new settings.

Put it to the test to check if the new memory settings are effective. Try to run a big query which generated the ‘out of memory’ error before. You may have to try this a few times. If there are no errors anymore, it will spare you a lot of complaints and users will be thankful (or just thinking you’re doing your work).

When you configure a webpart for RSS feeds in a SharePoint 2010 site, you receive the following error:

ProtocolError occured trying to complete the request. The server returned a status code of : ProxyAuthenticationRequired and the status description is : "Proxy Authentication Required ( Forefront TMG requires authorization to fulfill the request. Access to the Web Proxy filter is denied. )"

Solutions:

There are two things you can do, but maybe just one will work. In my case, solution 2 was in the end the only solution after testing and investigating half a day.

Solution 1

1. Navigate to the virtual directory of the SharePoint site, like: C:\inetpub\wwwroot\wss\VirtualDirectories\yoursitename

2. In the root you will find the file web.config. Edit this file and search for the line with <system.net>. Now copy and paste the following lines and make sure you change the value proxyaddress to the address of your own proxy server:

<system.net>

    <defaultProxy enabled="true" useDefaultCredentials="true"> 

        <proxy bypassonlocal="true" proxyaddress=http://10.1.2.3:80 /> 

    </defaultProxy> 

</system.net>

3. Save the file and restart IIS. To reset IIS, click Start > All Programs > Accessories > right-click Command Prompt, select Run as administrator, type in iisreset, and press ENTER.

Solution 2

Configure ISA/TMG to allow unauthenticated traffic to the Internet. Just add a rule which allows the SharePoint frontend server to navigate to the Internet (network External) over port 80.  Rule settings:

Action: Allow

Protocols: HTTP (80)

From / Listener: hostname of your frontend server

To: External (Internet)