The Sharing Violation issue in HAZUS FIT is known, however the workarounds provided in the technical documentation do not seem to work.

I am running the HAZUS FIT and can typically go through the first to about third steps, project validation, building 100 year grid, and sometimes the shoreline wizard.  Other times, I get a sharing violation almost immediately.  I am running the FIT in ArcMap 9.2, with the appropriate service packs.  I am running the data through my local C:\ drive, not a network drive.  I am running no other programs, including Windows Explorer, during this time.  The sharing violation occurs in the \Misc folder consistently.

Any ideas for a workaround?  I’ve tried the listed ones, and have tried HAZUS help - they seem to be able to get the program to run properly.

Thanks,
Peter

Any ideas for a workaround?  I

Jonathon, thank you; I will give the Unlocker and if needed, the other steps, a shot.

Yes, HAZUS Help has been able to use my data and run through the FIT process - I have been unable to.  Appendix C has not helped either.

I’ll update after I give it another try.

Peter

Jonathon -

Here’s an update.  After running the program again, and inspecting Unlocker, it is ArcMap that is having a sharing violation with itself.  Windows Explorer is not even a process listed to unlock.  ArcMap keeps having a sharing violation with the /Misc folder.

I’m loathe to try uninstalling and reinstalling everything, but am getting to that point.

Peter

Well, Unlocker did not work.  All it found was ArcMap, so I’m going to try uninstalling everything, then reinstalling.  I did try upgrading to ArcSP6, but that did not help either.  Very frustrating!  I’ll update after the next steps.

OK, got it to work.  I took my system back to XP SP2, and Arc9.2, SP 5.  I think my issue was having aerial orthophotographs open within ArcMAP that were sourced from a network drive while using FIT.  Even though FIT does not need (or use) the photos (I was just using them as basemaps for viewing my data), NO data within the ArcMap session can apparently come from a network drive.  It must all be sourced from a local drive, regardless of whether or not FIT is actually using the data.  i knew this was the case for data I was working with, but did not suspect as much for supplemental data that was just open in ArcMap.

Now I’ve got to take the FIT results and bring them into HAZUS to estimate damages, we’ll see how that goes!

Pete

I’m glad you found a way to make it work!

Out of curiosity, since the HAZUS reinstall, do you still get the sharing violation when you bring layers in from the network drive? And does the sharing violation go away again when the networked layers are removed? Do you get the same problem with any networked layer? Or do some work with FIT?

If you can cause the violation to happen, and then fix it again, by adding and removing the layers from the network drive, then we will have pinpointed the problem to the networked files.

Of course, don’t try this little experiment until after your project deadlines.

Jonathon -
The problem does continue with bringing in layers from the network drive, while using FIT.  There’s no issues bringing layers in, but one cannot move through the FIT wizards with the layers present (i.e., I could bring in base orthophotography, delineate the shoreline, then remove the orthophotos, and use the FIT shoreline wizard - if I kept the orthophoto layer present when the shoreline wizard was open, the sharing violation would occur).  I did find that that I can bring in network layers - and keep them active - after the shoreline wizard is completed.  I did encounter this same sharing violation with each previous step of the FIT wizards (i.e., project validation, build floodplain, shoreline).  Hope this helps!

Pete

So the FIT wizards work so long as you are not simultaneously using layers from a network drive.

I’m glad that you figured out a way to solve this one.  This will be a useful workaround until this problem is fixed in a future version of HAZUS.

—-

This thread is now closed.

(If someone has found a better workaround, or if a new HAZUS update corrects this error. Please post the details in a new topic and I will re-open this thread.)