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.
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
K2 – “Insufficient SQL database permissions for user in database ‘SharePoint_Config’ on SQL Server instance ‘WSS1′.
By peter.stilgoe
If your seeing the below error in your event viewer:
Error:
“Insufficient SQL database permissions for user in database ‘SharePoint_Config’ on SQL Server instance ‘WSS1′. Additional error information from SQL Server is included below.
EXECUTE permission denied on object ‘proc_putObject’, database ‘SharePoint_Config’, schema ‘dbo’.”
Solution:
The K2 Server account must be part of the Site Collection Admin Group in MOSS.
Save to sql server failed no description found
By peter.stilgoe
When trying to create an SISS package in sql server managament studio using the export wizard you get the following error message at the last stage:
“Save to sql server failed no description found”
To fix this you need to reregister the following DDL’s
Regsvr32 msxml3.dll
Regsvr32 msxml6.dll
Now when you try & save you SISS package it should go through with no problems.
Import data from CSV and SQL to a SharePoint list
By peter.stilgoe
This SharePoint feature allows you to quickly import data from a CSV file or a SQL stored procedure to any custom SharePoint list.
Once you have added the solution to your farm and activated it on your site collection an additional menu option will be available on the Action menu of each custom list that will take you to the import CSV or SQL page.
Simply select which option you want – either import from a CSV file or import from a SQL stored procedure. Next, browse to the CSV file or enter the SQL connection and name of the stored procedure and hit the Import button.
There is a check box option to delete all items from the list before doing the import which is not selected by default.
Sharepoint – Creating Content Databases
By peter.stilgoe
When you create a content database in Sharepoint through the central admin it is created with the following characteristics:
Recovery Model: FULL
Auto growth: 1mb
Log file growth: 10%
The one we are concerned with here is the Auto growth being set to 1mb. This means is we upload a 50mb file, the Db has to grow 50 x 1mb which causes performance issues. Also if a database auto grow occurs whilst being used by end users all web sites inside that site collection will stop while the database allocates more space. Also you will be pretty much guaranteed to get database fragmentation.
Its better to create your content databases manually and set the size you expect it to grow to from the outset. Then set a quota in Sharepoint so that the DB cant grow any more once it hits the size limit.
Note: if you do create via SQL ensure the DB settings are Latin1_General_CI_AS_KS_WS



May 5th, 2010

![Recommend [pstilgoe]](http://s3.amazonaws.com/arkayne-media/img/badge/logo-recommend-badge-medium.png)