After creating a Business Data Connectivity Service Application in SharePoint 2010 I wasn’t able to access the service application with the BDC models, external systems and external content types. The error message I received was: "There are no addresses available for this application.”

Error description

The error message itself and the log files were pointing me nowhere…

Solution

Although the Business Data Connectivity Service was started using a PowerShell script right after the configuration of the service application it seems that they didn’t work together. Maybe this is due to the fact that a timer job is involved if you start this service.

Finally I did an iisreset and everything worked fine. Great this method still works in SharePoint 2010.

Recently I got an error where a web couldn’t be created in SharePoint Server 2007 with Service Pack 2. Reviewing Event Viewer and ULS Log pointed me in the right direction with a SQL Server deadlock…

Error description

This is the error message I got when I tried to create a site:

Event log message was: 'Failed to initialize some site properties for Web at Url: [URL]'. Exception was: 'Microsoft.SharePoint.SPException: Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) ---> System.Runtime.InteropServices.COMException (0x80004004): Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))

After reviewing the ULS log I found an error message pointing me to the final solution:

Unexpected query execution failure, error code 1205. Additional error information from SQL Server is included below. "Transaction (Process ID 121) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."

Solution

You need to install Service Pack 3 for SQL Server 2005 which contains a fix for resolving this issue.

Microsoft support: http://support.microsoft.com/kb/953948/EN-US

Note: I have seen the same error message where this solution is not applicable because of a minor difference regarding the error message. Please carefully review your log files to check if this solution fits your needs or not. 

I’m running Windows Server 2008 on my notebook and was wondering about a slow boot time showing applying computer settings which took more 3:06 minutes. Now I have found the solution and my system start takes only 1:50 minutes which is an enhancement of more than one third. So here is the detailed description of what I have done…

Error description

When you take a look at the event viewer you will see the following warnings:

• EventID: 6005
  The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (CreateSession).
• EventID: 6006
  The winlogon notification subscriber <GPClient> took 134 second(s) to handle the notification event (CreateSession).

Solution

My notebook smart card reader which caused trouble with the Group Policy Client. After disabling the smart card reader in device manager my system boot was faster.

Although 1:50 minutes isn’t as fast as my Vista partition it saves time…

Last month I got some error messages after creating a customized onet.xml and content types in SharePoint. One of the error messages was: A duplicate name "Item" was found. After taking a look into the SharePoint log files I found more details:

I tried to create a website based on my custom ont.xml and my custom content types. The reason for this error message was a spelling error in my custom content type:

<ContentType ID="0x010100............08}"

After removing the bracket at the end the site creation process was successful.

If you want to extract an assembly (.dll) from the Global Assembly Cache you can use the following method which doesn't require a third party tool:

Open the Explorer and go to "Tools" in order to map a network drive.

There you can enter the server name and the folder: \\SERVERNAME\FOLDER. In my case it is: \\moss2007\c$\windows\assembly. You don't need to share the folder if you are an administrator. After the mapping you can browse the GAC and extract an assembly.

If you try to copy a large file from a network share sometimes Windows Server 2008 or Vista freezes the network connection although you have Service Pack 1 installed. After that you have to reboot in order to get your network connection to work. You can find some discussions without any solution. I had the same problem and this workaround works for me:

1. Never click at the "More information" button which is calculating the speed. Since I don't look at the information even file copies of 26GB are working - up and down.
2. Copy large files one by one using the crtl+c key combination.
3. Don't drag and drop files or folders.

I hope it works for somebody too.