"You are not licensed for Geodatabase Editor"

[MarkParr1]

I am running 10.1 SP1 on a Windows 7, 64-bit machine with 28GB of RAM and a 2TB drive. I recently started getting the error "You are not licensed for GEodatabase Editor." whenever I try to do any sort of geoprocessing. This perplexes me to no end as I'm trying to reproject a shapefile and I have never heard of the Geodatabase Editor. What the heck is it? It isn't an extension that I've ever heard of. I've been running 10.1 SP1 for a few months now and did not have this trouble previously. I have checked the .Net framework and I'm running the most recent version, 4.5.

Any thoughts? I'm about to submit a ticket.

Thanks!

[JoelCalhoun]

I am not sure if this is your issue but I began receiving this same message after I installed the 64-bit Background Processing service pack that was released with Service Pack 1. (Note: This is a separate install from Service Pack 1)

I uninstalled just the 64-bit Background processing piece and I was then able to perform geoprocessing operations again.

If you have this installed and you don't need to run any geoprocessing operations or python scripts in 64-bit then I would try uninstalling this component.


Good Luck,



Joel

[BrianZwilling]

I also get this message intermittently when doing geoprocessing tasks.  I am running 10.1 sp1 with windows 7 64 bit.  i don't have the extension installed, so it must be some other issue.  it is hard to pinpoint the problem because i will run a task and get the error, and then run the exact same task in the same session and it works fine.  Any advice would be greatly appreciated.

Thanks

[michaelcollins1]

This has been happening for a while at my company to various individuals...I wonder why ESRI hasn't replied to this yet? I can't even run the buffer tool.

[JoeBorgione]

Just my $00.02: contact tech support and start an incident...

[michaelcollins1]

The work-around is to turn off the background processing under "Geoprocessing Options".

[JackBeers_III]

Have you tried to roll back your install to only Service Pack 1.  You can remove updates separately.  Not everyone needs to install every patch.  Although ESRI has said that the new background processing is working via 64-bit, that doesn't necassarilly make it useful.  I've found it to still be clunky when operating with background processing.  I agree with @mcollinsamec, disable background processing.  If you do like it, you should open a support ticket like @jborgion said.

[JorgeOrellana]

We have experienced this issue but only on our VM server. It has not impacted any of our laptops/desktops what we have Arc10.1. And like others are reporting, Disabling background geoprocessing makes the error go away.

Cheers

[JorgeOrellana]

Has anyone found a solution to this? The other thing I have noticed is that we are only getting this error on newer machines. My machine which is about 2 years old does not see that error, but our new VMs and a couple of my colleagues that received new computers are getting that error, one of them is even getting it when he opens an MXD, not even trying to geoprocess.

Disabling background geoprocessing works but there must be a reason why it works fine on some machines and others are not.

Jorge

[KevinHibma]

Has anyone submitted a tech support call? If so, could you post the incident number?

I can't make this happen on my machine, and nobody here within Esri has ever encountered it, so I'd like to better understand the circumstances that make it happen.
Can anyone provide further details?
-What license do you currently have (basic, standard, advanced - floating or single use)?
-Does your license expire? If so, is it near expiring?
-This error ONLY happens with 64 bit BG installed and executing tools there? (or 32bit Background, or Foreground, or?)
-Any particular tools, or ALL tools?
-Do you have other Esri software installed (Engine, Server, etc)?