ERROR 000047: Could not open locator workspace

[Anonymous User]

Running ArcGIS 10 (Build ) on 64bit Windows 7. When trying to create a new locator (any) within a specific folder or a file geodatabase within that folder, I recieve the following error message: ERROR 000047: Could not open locator workspace. I noticed an archived forum post addressing the same issue from back in 2009 with no responses (http://forums.esri.com/Thread.asp?c=93&f=1113&t=284837). The Help text is not very helpful in finding a solution. Has anyone else run into this and have any ideas on what the problem is or a work around?

Thanks,
James

[MichelleBoivin]

I just got off the phone with ESRI and we were trouble shooting some issues. In my situation, it appears that the address locator will work with a feature dataset, but not if a network has been built. Once I deleted the network, I was able to use the original data. Still unacceptable and still have to modify processes from what is standard practice (not to mention discussed by ESRI), but at least I  know what the issue is.

This is unacceptable.
SOME clients cannot install service packs the day they are released to accomodate such basic necessities. The reason they cannot is because they have other, 3rd party products that must be certified against those service packs, which takes time.

And forcing me to keep my reference data outside a feature dataset - unacceptable. My client has numerous relationship classes associated with addresses and centerline data.  To restructure this is a major pain.

I was never able to get the locator built within my SDE connection (oracle 11gR2, SDE 10 sp1, direct connect).  I was able to copy the data to a file geodatabase and build it there.

[ShaunConway]

[INDENT]

I experienced similar trouble in ArcGIS 10. I believe the problem stems from creating an address locator based on a reference dataset that is located in a feature dataset. A workaround is to store your original reference dataset (or a copy) in the geodatabase, but not in a feature dataset. You can then create the address locator.

[/INDENT]

I was experiencing the same issue, but was successful with an alternative workaround. The reference data was within a feature dataset and the output address locator tool was defaulting to storing the new address locator with that same feature dataset. As an alternative to the above solution of moving/copying your reference data outside of a feature dataset, I was successful with simply changing the output address locator parameter to creating the address locator outside the feature dataset.

And with that said, I would like to add my support to getting ESRI to fix this issue. If an address locator cannot be created within a feature dataset, don't have the tool default to creating the address locator within a feature dataset and then provide a non-descript error. It took a few hours to resolve this issue from initial error to finding this thread.

[JillFischer]

I had the same problem...thanks for the tip on changing the location.  By default, in older versions it put it in the correct location, so I didn't even check that.  One more note from me is that it still didn't work by using Arc Catalog.  I had to use the Create Address Locator from Tool Box before I could get it work.  I am working in a SQL Server Express 2008 environment with ArcGIS 10....just thought I would throw that out there for another tip for anyone else have this problem.

[wcl]

Running ArcGIS 10 (Build ) on 64bit Windows 7. When trying to create a new locator (any) within a specific folder or a file geodatabase within that folder, I recieve the following error message:   ERROR 000047: Could not open locator workspace. I noticed an archived forum post addressing the same issue from back in 2009 with no responses (  http://forums.esri.com/Thread.asp?c=93&f=1113&t=284837). The Help text is not very helpful in finding a solution. Has anyone else run into this and have any ideas on what the problem is or a work around? 

Thanks, 
James

I'am Chinese IT'develpoer ,English is not well.I use ArcGIS Server 10 and oracle 10g,and met same obstacle with ArcCatalog .But I solute this problem ,instead ArcMap create locator.In ArcMap ,no this bug.
My Email:p_paul2008@126.com