Is this going to be a new fix for NIM090672

3999
3
Jump to solution
01-05-2015 06:55 AM
Highlighted
Regular Contributor

Here is the technical article. 41119 - NIM090672: Specific Microsoft updates may result in data corruption with file geodatabases o...

About 6 months ago this randomly happened to our server.  I contacted ESRI Tech Support and they gave me a work around because the hotfix didn't work.  I recently upgraded our servers to Server 2012 R2 and installed ArcGIS 10.3 hoping the problem would be gone but it still persists. Is there going to be a fix that works for this?

Thanks

Reply
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Regular Contributor

ESRI was able to help me resolve the issue.  I was getting the same error that is described in the above NIM article but the issue was something else.

Our IT staff updated our Anti-Virus software when the issue began which then blocked ArcGIS programs from creating feature classes in a file geodatabase on a network share.  We are in the process of creating exceptions for our ArcGIS programs and extensions.

Thanks ESRI for resolving this issue!

View solution in original post

Reply
0 Kudos
3 Replies
Highlighted
Esri Notable Contributor

That nimbus bug is marked as "as designed" because the problem was caused by a Microsoft patch. A Microsoft patch due out in August 2013 was supposed to fix it. If you're having a similar problem, please contact technical support to report it.

Melita

Highlighted
Regular Contributor

Thanks, ESRI got in contact with me and we are going to address the issue again soon.

Steven

Reply
0 Kudos
Highlighted
Regular Contributor

ESRI was able to help me resolve the issue.  I was getting the same error that is described in the above NIM article but the issue was something else.

Our IT staff updated our Anti-Virus software when the issue began which then blocked ArcGIS programs from creating feature classes in a file geodatabase on a network share.  We are in the process of creating exceptions for our ArcGIS programs and extensions.

Thanks ESRI for resolving this issue!

View solution in original post

Reply
0 Kudos