Exception from HRESULT: 0x80040E2F

[Lenid2]

A user failed to create a folder in a WSS 3.0 library, while using Windows
Explorer's Web folder. We are now unable to create a new folder in this
specific library, even from WSS. When we click New/New Folder from this
specific library, we get the following error : Exception from HRESULT:
0x80040E2F. The problem only occurs with this specific library, not with the
other libraries.

Any idea on how to fix this?

[Corinne]

Hi,

This HRESULT simply means, "Violation of PRIMARY KEY constraint ", which
generally means you have entries in the database for this site previously,
possibly orphaned. You can have a look at this excellent post
http://blogs.msdn.com/krichie/archive/2006/07/25/678040.aspx
Hope this helps

Cheers,

"Lenid2" <Len...@discussions.microsoft.com> wrote in message
news:36E2EEC2-0BFC-4F64...@microsoft.com...

[Lenid2]

Thanks Corinne,

I came up to this blog when I searched for a solution, but my problem is not
a backup/restore issue.

I may have found what is the source of our problem. Yesterday, I tried to
copy content from the faulty library to a new one. When I tried to copy from
Web folder to Web folder, I received an error message stating that some
folder and file names were too long. However, when I tried to copy content
from faulty library to local hard drive, it succeeded with no error. So, I
decided to then copy content from local drive to the new library, but I got a
warning message stating that some of the files could not be copied. It came
out that only 660 out of the 745 files were copied in the new library.

Eventhough we are now be able to create new folders in this new library, we
now know that users will have to shorten their folders and files's name in
Sharepoint.

Still, I would like to have a solution to fix the "Exception from HRESULT:
0x80040E2F" error with the faulty library.

Any suggestion?

[johannesprinz]

I'm getting the same issue at the moment too when editing SPListItems through the SharePoint object model.

Did you ever find a resolution to this problem?

Cheers

[Lenid2]

Sorry for the late reply. Unfortunately, I didn't find a solution. I still
believe that our folders, sub-folders and file names are too long. We are
planning to move files to a new site and make a better use of metadata. We
also want to prevent the users from creating to many sub-folders with long
files names.

Cheers!

Lenid2

[samarjeetsinghtomar]

I am having the same problem,
I tried many things including stsadm -o upgrade etcs.
Even some of the patches. still same problem persists when i am trying to create a folder in particular list it gives excception HRRESULT: 0x80040E2F

All other list are ok .

Please post the solutions if any body finds.

-Sam

Lenid wrote:

Sorry for the late reply. Unfortunately, I didn't find a solution.

05-Jan-09

Sorry for the late reply. Unfortunately, I didn't find a solution. I still
believe that our folders, sub-folders and file names are too long. We are
planning to move files to a new site and make a better use of metadata. We
also want to prevent the users from creating to many sub-folders with long
files names.

Cheers!

Lenid2

"Johannes Prinz" wrote:

Previous Posts In This Thread:

On Tuesday, October 07, 2008 1:27 PM
Lenid wrote:

Exception from HRESULT: 0x80040E2F

A user failed to create a folder in a WSS 3.0 library, while using Windows
Explorer's Web folder. We are now unable to create a new folder in this
specific library, even from WSS. When we click New/New Folder from this
specific library, we get the following error : Exception from HRESULT:
0x80040E2F. The problem only occurs with this specific library, not with the
other libraries.

Any idea on how to fix this?

On Wednesday, October 08, 2008 3:43 AM
Corinne wrote:

Hi,This HRESULT simply means, "Violation of PRIMARY KEY constraint ", which
Hi,

This HRESULT simply means, "Violation of PRIMARY KEY constraint ", which
generally means you have entries in the database for this site previously,
possibly orphaned. You can have a look at this excellent post
http://blogs.msdn.com/krichie/archive/2006/07/25/678040.aspx
Hope this helps

Cheers,

"Lenid2" <Len...@discussions.microsoft.com> wrote in message
news:36E2EEC2-0BFC-4F64...@microsoft.com...

On Wednesday, October 08, 2008 8:39 AM
Lenid wrote:

Thanks Corinne, I came up to this blog when I searched for a solution, but my
Thanks Corinne,

I came up to this blog when I searched for a solution, but my problem is not
a backup/restore issue.

I may have found what is the source of our problem. Yesterday, I tried to
copy content from the faulty library to a new one. When I tried to copy from
Web folder to Web folder, I received an error message stating that some
folder and file names were too long. However, when I tried to copy content
from faulty library to local hard drive, it succeeded with no error. So, I
decided to then copy content from local drive to the new library, but I got a
warning message stating that some of the files could not be copied. It came
out that only 660 out of the 745 files were copied in the new library.

Eventhough we are now be able to create new folders in this new library, we
now know that users will have to shorten their folders and files's name in
Sharepoint.

Still, I would like to have a solution to fix the "Exception from HRESULT:
0x80040E2F" error with the faulty library.

Any suggestion?

"Corinne" wrote:

On Thursday, December 18, 2008 4:13 PM
Johannes Prinz wrote:

I'm getting the same issue at the moment too when editing SPListItems through

I am getting the same issue at the moment too when editing SPListItems through the SharePoint object model.

Did you ever find a resolution to this problem?

Cheers

On Monday, January 05, 2009 7:32 AM
Lenid wrote:

Sorry for the late reply. Unfortunately, I didn't find a solution.
Sorry for the late reply. Unfortunately, I didn't find a solution. I still
believe that our folders, sub-folders and file names are too long. We are
planning to move files to a new site and make a better use of metadata. We
also want to prevent the users from creating to many sub-folders with long
files names.

Cheers!

Lenid2

"Johannes Prinz" wrote:

EggHeadCafe - Software Developer Portal of Choice
ADO.NET: Optimistic Concurrency Updating Logic
http://www.eggheadcafe.com/tutorials/aspnet/dd273725-d01f-4364-9c32-e94f115255a9/adonet-optimistic-concu.aspx

[samarjeetsinghtomar]

I am having the same problem,
I tried many things including stsadm -o upgrade etcs.
Even some of the patches. still same problem persists when i am trying to create a folder in particular list it gives excception HRRESULT: 0x80040E2F

All other list are ok .

Please post the solutions if any body finds.

-Sam

Lenid wrote:

Sorry for the late reply. Unfortunately, I didn't find a solution.

05-Jan-09

Sorry for the late reply. Unfortunately, I didn't find a solution. I still
believe that our folders, sub-folders and file names are too long. We are
planning to move files to a new site and make a better use of metadata. We
also want to prevent the users from creating to many sub-folders with long
files names.

Cheers!

Lenid2

"Johannes Prinz" wrote:

Cheers,

Any suggestion?

"Corinne" wrote:

Johannes Prinz wrote:

I'm getting the same issue at the moment too when editing SPListItems through

I am getting the same issue at the moment too when editing SPListItems through the SharePoint object model.

Did you ever find a resolution to this problem?

Cheers

On Monday, January 05, 2009 7:32 AM
Lenid wrote:

Sorry for the late reply. Unfortunately, I didn't find a solution.
Sorry for the late reply. Unfortunately, I didn't find a solution. I still
believe that our folders, sub-folders and file names are too long. We are
planning to move files to a new site and make a better use of metadata. We
also want to prevent the users from creating to many sub-folders with long
files names.

Cheers!

Lenid2

"Johannes Prinz" wrote:

On Thursday, November 05, 2009 6:17 AM
Samarjeet Singh Tomar wrote:

"0x80040E2F" + "SharePoint 2007" + "Creating Folder"

I am having the same problem,
I tried many things including stsadm -o upgrade etcs.
Even some of the patches. still same problem persists when i am trying to create a folder in particular list it gives excception HRRESULT: 0x80040E2F

All other list are ok .

Please post the solutions if any body finds.

-Sam

On Thursday, November 05, 2009 6:18 AM
Samarjeet Singh Tomar wrote:

"0x80040E2F" + "SharePoint 2007" + "Creating Folder"

I am having the same problem,
I tried many things including stsadm -o upgrade etcs.
Even some of the patches. still same problem persists when i am trying to create a folder in particular list it gives excception HRRESULT: 0x80040E2F

All other list are ok .

Please post the solutions if any body finds.

-Sam

EggHeadCafe - Software Developer Portal of Choice
Custom Membership, Role and Profile: Silverlight RIA Service
http://www.eggheadcafe.com/tutorials/aspnet/ee9d9436-5e3c-4cb5-9323-68bc8ba3e476/custom-membership-role-a.aspx

[samarjeetsinghtomar]

I am having the same problem,
I tried many things including stsadm -o upgrade etcs.
Even some of the patches. still same problem persists when i am trying to create a folder in particular list it gives excception HRRESULT: 0x80040E2F

All other list are ok .

Please post the solutions if any body finds.

-Sam

Lenid wrote:

Sorry for the late reply. Unfortunately, I didn't find a solution.

05-Jan-09

Sorry for the late reply. Unfortunately, I didn't find a solution. I still
believe that our folders, sub-folders and file names are too long. We are
planning to move files to a new site and make a better use of metadata. We
also want to prevent the users from creating to many sub-folders with long
files names.

Cheers!

Lenid2

"Johannes Prinz" wrote:

Cheers,

Any suggestion?

"Corinne" wrote:

Johannes Prinz wrote:

I'm getting the same issue at the moment too when editing SPListItems through

I am getting the same issue at the moment too when editing SPListItems through the SharePoint object model.

Did you ever find a resolution to this problem?

Cheers

On Monday, January 05, 2009 7:32 AM
Lenid wrote:

Sorry for the late reply. Unfortunately, I didn't find a solution.
Sorry for the late reply. Unfortunately, I didn't find a solution. I still
believe that our folders, sub-folders and file names are too long. We are
planning to move files to a new site and make a better use of metadata. We
also want to prevent the users from creating to many sub-folders with long
files names.

Cheers!

Lenid2

"Johannes Prinz" wrote:

On Thursday, November 05, 2009 6:17 AM
Samarjeet Singh Tomar wrote:

"0x80040E2F" + "SharePoint 2007" + "Creating Folder"
I am having the same problem,
I tried many things including stsadm -o upgrade etcs.
Even some of the patches. still same problem persists when i am trying to create a folder in particular list it gives excception HRRESULT: 0x80040E2F

All other list are ok .

Please post the solutions if any body finds.

-Sam

EggHeadCafe - Software Developer Portal of Choice
Code Recommendations For COM+ VB Developers
http://www.eggheadcafe.com/tutorials/aspnet/1b191bc3-c66e-4480-9869-b803b114a18d/code-recommendations-for.aspx