Knowledge Base - Technical Articles


Technical Article   Problem:  NIM090672: Specific Microsoft updates may result in data corruption with file geodatabases or shapefiles created on a network share

Article ID: 41119
Bug Id: N/A
Software:  ArcGIS - ArcEditor 9.3.1, 10 ArcGIS - ArcInfo 9.3.1, 10 ArcGIS - ArcView 9.3.1, 10 ArcGIS for Desktop Advanced 10.1 ArcGIS for Desktop Standard 10.1 ArcGIS for Desktop Basic 10.1
Platforms:  Windows Windows 7, Server 2008 R2

Description

A recent Microsoft update (deployed as KB 2732673, KB 2775511, or KB 2824408) may result in data corruption when using ArcGIS on a Windows 7 system and writing data to remote data storage on a Windows Vista, Windows 7, or a Windows Server 2008/2008 R2 or 2012 system. This data corruption appears as truncation of a write request and has shown up in file geodatabases and shapefiles.

Additional Information

An error message referencing the ItemType appears when creating new datasets or items (tables, feature classes, feature datasets, raster datasets, and so forth) in a 10.x file geodatabase created on a network share.

For example, the following message is displayed when creating a new feature class:

"Failed to create feature class.
The item was not found. [ItemType:
{70737809-852C-4A03-9E22-2CECEA5B9BFA}]"

File geodatabases created with ArcGIS 9.3.1 return the following error when creating new datasets or items, renaming the file geodatabase, or accessing the geodatabase properties.

"Failed to connect to database.
This release of the Geodatabase is either invalid or out of data. [Invalid Geodatabase release]"

Cause

Microsoft has acknowledged the problem, identified the affected component as RDBSS.sys, and provided further details in this Windows SDK Support Team Blog.

How Microsoft made these updates available

In April 2013, Microsoft released hotfixes KB 2732673 and KB 2824408 to address specific issues. The KB 2775511 update is a cumulative update that is available exclusively through the Windows Update Catalog.

Because this update is available only through the Windows Update Catalog, the KB 2775511 update is not considered a security update by Microsoft and is not being deployed broadly.

Solution or Workaround

The update for KB 2732673 has been released as of August 13, 2013. The hotfix is available under Microsoft Knowledge Base article 2732673.

• If KB 2775511 has already been installed, install the update patch found at Knowledge Base article 2732673.
• If KB 2775511 is to be installed at some future date, install the 2732673 update patch now to mitigate any issues that may impact file geodatabases and shapefiles stored on network drives.

Additional Information and Updates
• August 26, 2013: Esri has completed testing Microsoft's fix for the file geodatabase issue and verified that it resolves the issue.
• August 14, 2013: Microsoft posted an update today on their Windows SDK Support Team Blog. The update states 'The update to the issue was released today. The update is available under KB article 2732673.'
• June 27, 2013: Microsoft posted an update today on their Windows SDK Support Team Blog. The update states 'The hotfix is currently still under development with the update being in testing. The update is on track to be released within the next 60 days (August 2013).'
• May 22, 2013: Microsoft is in regular communication with Esri and continues to have dedicated development staff working on the issue. A fix has not yet been identified.
• May 13, 2013: Microsoft has isolated the cause of this issue to an RDBSS.SYS component that was updated by a specific hotfix which is included as part of the Microsoft hotfix rollup KB 2775511. Additional information, including possible workarounds, can be found in this Microsoft Windows SDK Support Team Blog.
Esri and Microsoft continue to look for a solution to this issue.
• May 13, 2013: We have confirmed that the same issue occurs when working with shapefiles and results in an error message such as:
"Error opening feature class
Number of shapes does not match the number of table records".
• May 10, 2013: The specific Microsoft hotfix that exposed this issue has been identified. Esri and Microsoft are continuing to dedicate staff full-time to research the cause and provide a resolution as quickly as possible.
• May 6, 2013: Esri and Microsoft continue to work on this issue with dedicated full-time staff who are in regular, daily communication. These groups are currently working together with a simplified reproducible case.
• Our testing indicates that the behavior is reproducible with network shares created on Windows systems using the SMB 2.1 and SMB 3.0 protocols.
• Network shares created on Windows XP (SMB 1.0) and Windows Server 2008 (SMB 2.0) do not encounter this issue.
• The behavior is encountered when using a network share created on Windows 7 and Windows Server 2008 R2 machines.
• The issue is also not reproducible when the file geodatabase is created using the file geodatabase API.
Please contact Esri Support if other behaviors are noticed with new or existing file geodatabases after installing this specific Microsoft rollup.


Related Information


Created: 4/18/2013
Last Modified: 6/26/2014

Article Rating: (28)

Comments

By mumins - 06/25/2014 7:48 AM

The article is incorrect or the solution didn’t work.

We have two Windows 2008 R2 servers, both have KB 2775511 installed. We installed KB 2732673 on one of them, it did not fix the problem. The only real fix was to disable SMB v.2 completely on servers. http://support.microsoft.com/kb/2696547 It appears to me that the problem is in the way how ArcGIS deals with 0-length signal files (*.lock and similar). Since introduction of SMB v.2 (Windows Vista, 7, 2008) network file/directory metadata is cached at SMB client and there can be delays between file is created and it appears for the client app. The link http://stackoverflow.com/questions/5159220/windows-file-share-why-sometimes-newly-created-files-arent-visible-for-some-pe describes the situation where newly created files do not appear for about 10 secs. If ArcGIS is not aware of this, it could break down its functionality of writing network FGDBs.

Rating:

By nmanis - 11/14/2013 11:03 AM

Great article! It helped a lot!

@Knoche: For the hotfix released, it is available for Windows 7 SP1 only. Win7 without SP1 is no longer serviced by Microsoft for hotfix releases. @Rmiller22: The hotfix is now listed under Microsoft WSUS as well for IT departments not using Windows Update directly. We have no reports of the hotfix not resolving this issue.

Rating:

By Knoche - 10/17/2013 1:50 PM

The article is incorrect or the solution didn’t work.

I'm on Windows 7 Enterprise (no SP) and it's giving me the 'ol "Update not applicable" run-around. I'm definitely getting the error, though.

Rating:

By rmiller22 - 09/18/2013 3:46 PM

The article is incorrect or the solution didn’t work.

My IT department has applied the hotfix, but the problem is not solved.

Rating:

By jaugsburger - 09/04/2013 7:19 AM

Other - See details below.

Article updated.

By seckhardt - 09/03/2013 8:16 AM

The article needs to be updated.

It is now September and still no fix, no acceptable work-around, and no update.

By tguerrette - 08/26/2013 11:18 AM

The article needs to be updated.

The last update was from 5/6/2013. There should be more info available. We want to install this update but are waiting for an available fix.

Rating:

By hyslop - 08/23/2013 12:23 PM

Other - See details below.

It seems a fix was released on August 13 - see http://support.microsoft.com/kb/2732673 This is linked from the last update under "additional information and updates" - the SDK support team blog posting. I haven't yet tried the fix.

By plaidsox - 06/14/2013 7:14 AM

The article needs to be updated.

ESRI please fix. Out of the dozens, maybe even hundreds of different software titles we have in our offices yours was the only failure we found.

Rating:

By cbound@borton-lawson.com - 06/13/2013 5:06 AM

Other - See details below.

We recently ran some updates on our file server and started to encounter this problem. Strange thing was none of the 3 KB listed were installed. After going through the comments I saw what @support-ria-gis posted about there being 90 separate KB that were part of 2775511. Going through that list we found 1 of them had installed during our updates. It was KB 2709630. We uninstalled it, rebooted the server and one of our GIS people tested and the issue seemed to be corrected. Hopefully this might help others as well.

Rating:

By EsriSupportResources - 05/23/2013 5:01 PM

Other - See details below.

@jonathanchipman, the Esri "Known Issues" page that reported that a patch was available was in error. There is no patch available at this time. Please continue to watch this article for updates. - Esri Support Team

By nmanis - 05/23/2013 12:04 PM

Other - See details below.

@jonathanchipman, for the issue reported in this article with the 2775511 update, there is not an updated hotfix at this point yet from Microsoft. We are working on an update. At this time, the Microsoft recommendations are to uninstall the 2775511 update for the scenario or to disable SMB 2.0 on the servers until an update is released.

Rating:

By jonathanchipman - 05/22/2013 4:33 AM

The article needs to be updated.

Thanks for letting us know about this, but I'm a bit confused about whether or not there's a patch for this. On the Support/Known-Issues page, ESRI seems to say that there is a patch available for this in 10.1: http://support.esri.com/en/content/known-issues ... go to version 10.1: 04/24/13 – File geodatabases created on a network share are unusable after installing Microsoft hotfix rollup KB 2775511 on Windows 7 SP1 or Windows 2008 R2 SP1. (Patch Available) Clicking on the "Patch" link goes to this page: http://support.esri.com/en/downloads/patches-servicepacks/view/productid/66/metaid/1978 But the actual description of that patch doesn't seem to have anything to do with the Microsoft hotfix issue. Instead, it seems to be just a duplicate of the patch for the next item in the "Known Issues" list, which deals with licensed network datasets. Is there a patch for the Windows hotfix problem yet?

Rating:

By geodatagmbh - 05/16/2013 10:46 PM

Other - See details below.

We are using a netapp which has ntfs-shares. So no important article for us?

Rating:

By nmanis - 05/15/2013 6:42 AM

Great article! It helped a lot!

@Matt160. The uninstallation of the 2775511 does not lower your network security. The KB 2775511 update released by Microsoft is for performance improvements. It is not a security update and available only as an optional update.

Rating:

By matt160 - 05/14/2013 11:11 AM

The article needs to be updated.

Is there an update to a fix? "Please lower your network security," is not a real solution.

Rating:

By ssimpson - 05/13/2013 10:21 AM

The article needs to be updated.

One thing that wasn't mentioned is that Microsoft did not distribute this update via Automatic Updates, but rather via something called Microsoft Update Catalog. This means that your IT department had to know about the update, and then manually download and lease it to everyone it without testing ArcGIS on a test system first.

Rating:

By pitks - 05/13/2013 8:52 AM

The article needs to be updated.

There is a additional workaround for this problem: Follow this Microsoft article and disable SMBv2 on a client or server PC (or both). http://support.microsoft.com/kb/2696547

Rating:

By badgersatfrogs - 05/09/2013 3:42 PM

Great article! It helped a lot!

our organisation rolled back the hotfix to work around this issue.

Rating:

By Candy - 05/07/2013 4:49 PM

Other - See details below.

We have only just experienced the hotfix KB 2775511. Our users are reporting an inability to edit shapefiles as well. Anybody also having this problem? File based geodatabases are definitely not working post hotfix implementation. As well roaming profiles with, style manager can be corrupted

Rating:

By D.E.Smith99 - 05/01/2013 1:36 PM

Other - See details below.

any update on this? any? at all?

Rating:

By dvela - 04/29/2013 9:17 AM

Other - See details below.

I did a quick test with an existing fgdb and if you add a field and try to do a calculate it corrupts the data.

Rating:

By jwatt - 04/26/2013 4:01 PM

Other - See details below.

Has anybody tried disabling SMB2 and SMB3 and seeing if there are any problems just using SMB1?

By matt160 - 04/26/2013 11:00 AM

Other - See details below.

@ntobin We do not have that KB installed except when it was applied by KB2775511. We did find if a file is made in 10.1 it was ok but most of our files are in 10.0.

Rating:

By matt160 - 04/26/2013 10:54 AM

Other - See details below.

@nemesisity "Matt160, how is it poor programming on ESRI's part when a Microsoft service pack breaks what used to work? Nice logic." Well not a single other application was impacted in our forest, even some old 16 bit apps are working just fine. We determined it was KB2775511 on April 2nd and submitted it to ESRI. And from a sysadmin's view this is some of the poorest software out there when it comes to deployments. There is your logic.

Rating:

By ntobin - 04/26/2013 7:35 AM

The article needs to be updated.

As someone else stated, I'd like to know if one of the hotfixes included in this rollup package KB258106 ( http://support.microsoft.com/kb/2581608 ) is the cause of this. So far in testing I haven't experienced any issues, but I'm about to do a major rollout and this would be helpful. Has anyone experienced any issues with this individual hotfix implemented (KB2581608)?

Rating:

By mmestrov - 04/25/2013 10:58 AM

Other - See details below.

Do you have an ETA on when the patch might be ready?

By AlexZendel - 04/25/2013 10:10 AM

The article needs to be updated.

Does this affect/corrupt/damage existing FGDBs and/or their feature classes if the hotfix is installed down the road? This possibility was not mentioned, so I'm assuming not. Having to create FGDBs locally first isn't a big deal. Losing existing data is. Some confirmation that our existing data is safe would be helpful and appreciated.

Rating:

By solxenos - 04/25/2013 9:59 AM

Other - See details below.

Well, not pointing any fingers or saying it's poor programming. But I have heard that another possible workaround is to create a File Geodatabase with version 9.3 or 10. So maybe it didn't break the older FGDBs for some reason? This is just another good example of why you wait until version 10.3.1 SP2.... if you can. Sorry for those who cannot find a suitable workaround and those who have to waste time with a workaround.

Rating:

By nemesisity - 04/25/2013 9:10 AM

Great article! It helped a lot!

Good luck on finding a solution to this one. Matt160, how is it poor programming on ESRI's part when a Microsoft service pack breaks what used to work? Nice logic.

Rating:

By support-ria-gis - 04/25/2013 6:32 AM

Other - See details below.

Could you be more specific : the KB 2775511 contains 90 other separates KB previously released. (see "Hotfixes that are included in this update rollup" in http://support.microsoft.com/kb/2775511 ) Maybe only one of this 90 hotfix should be stop by our IT dpt Maybe stopping the deployment of this KB is totally useless if the 90 hotfixes are installed one by one.

By weberj2011 - 04/25/2013 5:45 AM

Other - See details below.

1) You guys need to put the date and times on the top header of these bug reports, At the bottom makes it hard to find. 2) Your email was sent very late in the game, you need to speed that up. 2) You should tell how soon we can expect this will be fixed.

Rating:

By matteitrem - 04/25/2013 5:27 AM

I would like to see a new article that discusses the topic outlined below.

Can you be more specific on what constitutes a network share? Is this any and all, regardless of underlying network file system or how the network share was established?

Rating:

By ILGW75 - 04/25/2013 5:11 AM

Other - See details below.

The workarounds are not good for our organization as we are on citrix and most users are not allowed to store anything on theri local machine. Good luck with finding a fix, and thanks for the notification. Will notify our users.

Rating:

By matt160 - 04/25/2013 4:59 AM

Other - See details below.

It was a bit sad the users figured this out and your tech support failed. Now in the future are you going to work with the major software vendors to remain current or are we going to have to leave our system unpatched due to poor programming on your part?

Rating: