Unable to add selected web part

By peter.stilgoe









Unable to add selected web part(s)

QueryListPart: A Web Part or Web Form Control on this page cannot be displayed or imported. The type could not be found or it is not registered as safe.

- Make sure the webpart is registered as safe in the web.config

- Make sure the assembly is accessible and in the bin folder

- Make sure the assembly name in the *.webpart definition file, matches the assembly name in the safe control element in web.config

- Make sure you don’t have more than one *.webpart file for the same web part in the web part catalog. This may happen if you changed the name of the *.webpart file.

- Restart IIS to start clean. Attach the debugger to the w3wp.exe process and try to load the page with the rogue web part. This way you can determine the exact location of the assembly you are loading.

- Check if the web part class exists by opening the assembly with reflector. This might sound funny, but in a bigger team, when different versions of assemblies are flying around it is very easy to overlook something and to use the wrong version, which so happens does not contain the web part class at all.

Thanks to http://www.mikhaildikov.com/

  • Share/Bookmark

Leggi tutto

Error (Exception from HRESULT: 0×80004004 (E_ABORT))

By peter.stilgoe









This error usually occurs in Sharepoint when the transaction log is full or no drive space available to it on the SQL server in your farm.

You will usually get the error when trying to create new content etc.

  • Share/Bookmark

Leggi tutto

An error occurred processing the data view. The XslText property is empty

By peter.stilgoe









If you are getting the error:

‘An error occurred processing the data view. The XslText property is empty’

You have probably inserted an extra dataview on your page, check your page & remove the extra data view you accidentally inserted & your error will go away.

  • Share/Bookmark

Leggi tutto

Sharepoint Javascript Error: ‘style.display’ is not null or not an object

By peter.stilgoe









If you are receiving the following error when trying to access the ‘edit’ menu of a webpart on a page:

‘style.display’ is not null or not an object

It is likely that you have some random/extra code in another webpart on the page, this typically happens if you cut & paste text from another location onto the page & it also brings over some formatting chars which upsets Sharepoint. Either:

a) Remove the offending text from another webpart on the page

b) Use something other than IE like Firefox or Google Chrome, typically using another web browser you will be able to edit the troublesome webpart.

  • Share/Bookmark

Leggi tutto

K2 deployment error: The partner transaction manager has disabled its support for remote/network transactions

By peter.stilgoe









When deploying a new K2 workflow / process you get an error message containing:

The partner transaction manager has disabled its support for remote/network transactions

First check on the application server(s):

1. Go to “Administrative Tools > Services”
2. Turn on the “Distribute Transaction Coordinator” Service if it is not running

If you still get the error:

First verify the “Distribute Transaction Coordinator” Service is
running on both database server and application servers

1. Go to “Administrative Tools > Services”
2. Turn on the “Distribute Transaction Coordinator” Service if it is not running

If it is running and its not running on the same server as the SQL Server:

1. Go to “Administrative Tools > Component Services”

2. On the left navigation tree, go to “Component Services > Computers
> My Computer” (you may need to double click and wait as some nodes
need time to expand)

3. Right click on “My Computer”, select “Properties”

4. Select “MSDTC” tab

5. Click “Security Configuration”

6. Make sure you check “Network DTC Access”, “Allow Remote Client”,
“Allow Inbound/Outbound”, “Enable TIP” (Some option may not be
necessary, have a try to get your configuration)

7. The service will restart

8. YOU MAY NEED TO REBOOT YOUR SERVER IF IT STILL DOESN’T WORK

On the application server(s) use the same above procedure to open the
“Security Configuration” setting, make sure you check “Network DTC
Access”, “Allow Inbound/Outbound” option, restart service and computer
if necessary.

On you SQL server service manager, click “Service” dropdown, select
“Distribute Transaction Coordinator”, it should be also running on
your server computer

  • Share/Bookmark

Leggi tutto

Deploying K2 process: Error occurred adding the feature to the farm Server was unable to process request. —> Access denied.

By peter.stilgoe









When deploying a K2 process you get the following error:

Task Error: System.Exception: Error occurred adding the feature to the farm. —> System.Web.Services.Protocols.SoapException: Server was unable to process request. —> Access denied.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

This is normally a permission problem & you should check the following & make any changes that are required:

1) Check that the MOSS app pool account has Site Collection and Farm Admin Rights and is also a local administrator.

2)Check that the MOSS app pool account is given dbo permission on the SP Admin Config database.

3)Check that the MOSS app pool account is granted modify permissions: [Program Files]\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\ and \12\ISAPI folders.

4) Make sure the MOSS app pool account is given K2 export rights.

5) Make sure the “K2 Workflow Integration Content Types” in Central Admin > K2 for SharePoint has been activated.

You may also need to to do an iisreset.

If all of the above are present you should be able to publish your workflow without experiencing the above error.

  • Share/Bookmark

Leggi tutto

Microsoft.SharePoint.SPException: A duplicate name “Report” was found

By peter.stilgoe









When you try to activate ‘Office SharePoint Server Enterprise Site Features’ you get the following error:

Office SharePoint Server Enterprise Site Collection features12/09/2008 16:00:51.91
w3wp.exe (0x1FB8) 0x17B8 Windows SharePoint Services
General 8grz High The feature
’8581a8a7-cf16-4770-ac54-260265ddb0b2′ depends on feature
’43f41342-1a37-4372-8ca0-b44d881e4434′ which failed to activate:
Microsoft.SharePoint.SPException: A duplicate name “Report” was found.

The problem occurs if you have created a custom content type called ‘Report’ this is because when you activate ‘Office SharePoint Server Enterprise Site Features’ it trys to create a system content type called ‘Report’. The workaround is to rename your custom content type from ‘Report’ to something similar.

  • Share/Bookmark

Leggi tutto