nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Find more posts tagged with

Accepted answers

All comments

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

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.

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.

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.

MichelleBoivin

I agree that this is unacceptable. Today I am having the exact same error trying to create an address locator as well. My centerline file is also in a network dataset in SDE (I have sysadmin rights to the server and SDE). I attempted everything mentioned within the threads; storing it outside of the dataset (which is where I want it anyway), renaming it to keep it short, etc. Nothing worked until I imported the feature class outside of the dataset so it was a stand alone feature class. There should not be any reason as to why a user needs to maintain an extremely important dataset in two places due to a bug.

For the record, I am on AGD 10.0, SP3, Windows XP, using direct connect.

JessiePechmann

Got it to work!
I got this same error while building a locator from a feature dataset. I had to change the default to something I typed in for the output file. Worked then.

BradNiemand

I can't reproduce this issue on 10.0 SP2. I have a street centerline featureClass that is stored in a featureDataset and the locator builds with no issue. The one issue that I see most often is that, by default, the output location for the locator is within the featureDataset and that is when creation fails. If this is not what you are seeing, I would suggest logging a call with support.

Brad

SeanMoran

If your reference data is in a dataset then ArcCatalog will try to create the locator in that dataset which will give you the error you mentioned.

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.

I believe this is a bug that ESRI should acknowledge and address. I should be able to create an address locator based on a centerline file that is stored in a feature dataset.

TroyNagle

If your reference data is in a dataset then ArcCatalog will try to create the locator in that dataset which will give you the error you mentioned.

BradNiemand

Once you created it in a FileGDB can you copy it into SDE? I think it still may be related to the long name issue I mentioned before.

Are you trying to store the locator within a feature dataset?

Brad

AnneShort

It worked from a FGDB saving into a FGDB. Is also worked from the SDE database saving to a file folder. Any thoughts as to why I can't save it within the SDE. It's not like I can assign SDE privledges to the database itself, I have to do that to each feature dataset.

BradNiemand

When you add a reference featureclass to the create locator tool it uses some logic to try and determine what reference data it thinks that you are adding. I your case you probably don't have a lot of the recognized names for the fields and therefore it thinks that it is a Alternate Name table. Do you switch it back to Primary Table? With regards to the output address locator, it will either use the last place that you tried to store a locator or the same place where the reference data exists. It also appends part of the tool name to the name of the reference data so, yes it can be quite long.

Have you tried to copy your data into a FileGDB and see if you can create a locator in the FileGDB? Maybe even try to store the locator in a Folder instead of in SDE?

Brad

AnneShort

Unfortunately renaming my connection string didn't work.

Two things I've noticed - anytime you add a reference featureclass it is automatically set to the default Role of Alternate Name Table rather than the Primary table. The output address locator name it defaults to is also really long.

Brad, do you have any other things I could try, or do I need to contact tect support?

AnneShort

It could be a known issue with long connection names. Is the direct connect string really long?

Brad

Yes it is! I'll rename it and see if I get better results thanks.
-Annie

BradNiemand

It could be a known issue with long connection names. Is the direct connect string really long?

Brad

AnneShort

What version of ArcGIS are you using? What database are you using? What version of SDE are you using? What are your database permissions and what type of connection are you using (direct connection or SDE connnection)?

Brad

ArcGIS 10 SP2, Enterprise SDE (SDE securities), ArcSDE 10 SP1, direct connection, connected as SDE user

BradNiemand

I got the same error message when trying to run 'Create Address Locator' today. No one is connected to my SDE database, and I can clearly connect through ArcCatalog to the reference featureclass. Please let me know if you hear anything.

-Annie

What version of ArcGIS are you using? What database are you using? What version of SDE are you using? What are your database permissions and what type of connection are you using (direct connection or SDE connnection)?

Brad

AnneShort

I got the same error message when trying to run 'Create Address Locator' today. No one is connected to my SDE database, and I can clearly connect through ArcCatalog to the reference featureclass. Please let me know if you hear anything.

-Annie

BradNiemand

How large is your reference data? Do you have any of the service packs installed (sp1 or sp2)? Can you provide me with your reference data so that I can try it on my side?

Brad

Anonymous User

Simple, and that seems logical, but one of the first things I checked was permissions.

BradNiemand

My first thought would be that you don't have access to the location that you are trying to create the locator in.

Brad

Anonymous User

Thanks Joe. Seems this has been an issue for quite some time.

JoeBorgione

This isn't much help, but here's a link to an even earlier thread: http://forums.esri.com/Thread.asp?c=158&f=2284&t=265675

Perhaps you need to log a bug with support?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.