topic Re: Failed to connect DB - Bad login user in ArcGIS Enterprise Questions

Failed to connect DB - Bad login user

MaximSpikin — Sun, 01 Jul 2012 09:35:00 GMT

1) installed:
   - pure OS - MS Server 2008R2 Sp1
   - ArcGIS for Server Workgroup Standard 10.1;
   - ArcGIS for Desktop Standard (ArcEditor) 10.1;
   - ArcSDE Workgroup 10.1 with MS SQL Server 2008R2 Express from ArcGIS Server DVD (Windows Authentication)

2) authorizing new licenses - all OK

3) in ArcCatalog:
   - add Database Servers
   - create a new geodatabase (see a progress indicator), but if try to connect to the geodatabase get the following message
[ATTACH=CONFIG]15633[/ATTACH]

What is wrong ????

P.S. As I understand the problem in the licensing arcSDE
[ATTACH=CONFIG]15632[/ATTACH]

Re: Failed to connect DB - Bad login user

LaurynasGedminas — Fri, 13 Jul 2012 19:18:11 GMT

Hello,
You have to give arcgis server account, and your domain account permission to create geodatabase on SQL Server.
Use SQL Server Management Studio to give permissions

Laurynas
GIS Analyst

Re: Failed to connect DB - Bad login user

Anonymous User — Fri, 17 Aug 2012 15:12:53 GMT

Original User: wpgis5673

Having the same issue. Did you have any luck resolving?

Re: Failed to connect DB - Bad login user

PhillipWaldron — Mon, 20 Aug 2012 13:42:28 GMT

Thank you for your patience, this issue is related to an existing bug,   NIM080151. "Accessing new geodatabase in a sde workgroup if it is enabled using �??enterprise�?� license failed with error message �??Failed to connect to database. Bad login user. Success�?� instead of �??license is not valid�?�

One will get error �??Failed to connect to database. Bad login user. Success�?� because of a missing registry key related
to ArcSDE Workgroup licensing.

1. Open registry and you will notice that the entry 'ArcSDE_License' is missing:
'HKEY_LOCAL_MACHINE', 'SYSTEM\CurrentControlSet\Services\MSSQL$sqlexpress'

2. Now , manually create an 'ArcSDE_License' entry as New String Value.   You will get the needed value
for this entry with steps below:
    a. Use the following URL to generate ECP file: https://customers.esri.com/index.cfm?event=pub.ecpAuthorizations
    b. Modify and copy string from ECP file into the ArcSDE_License entry.

3. Relaunch ArcCatalog and one will be able to create a new geodatabase, access properties, and create new feature classes without issue.

This should work to get your ArcSDE Workgroup to work for you.

Thank you,

Phillip W.
Geodata Analyst

Re: Failed to connect DB - Bad login user

Anonymous User — Mon, 20 Aug 2012 13:43:24 GMT

Original User: wpgis5673

Issue identified as bug by ESRI tech support. Workaround below:

[Synopsis]:      Accessing new geodatabase in a sde workgroup if it is enabled using enterprise license failed with error message Failed to connect to database. Bad login user. Success instead of license is not valid .

[Nimbus BugID]: [NIM080151]

[WorkAround]:     Manually create a new registry key 'ArcSDE_License' entry as New String Value under
                 'HKEY_LOCAL_MACHINE', 'SYSTEM\CurrentControlSet\Services\MSSQL$sqlexpress'
                  Modify and copy string from ECP file into the ArcSDE_License entry.
                  [To get ECP File, go to site: https://customers.esri.com/index.cfm?event=pub.ecpAuthorizations]

Re: Failed to connect DB - Bad login user

PhillipWaldron — Mon, 20 Aug 2012 16:29:45 GMT

Just as a correction, the correct NIM number for this bug is:

[NIM]:             NIM083155

[Synopsis] :     Error �??Failed to connect to database. Bad login user. Success�?� occurs after creating a geodatabase with
                     ArcSDE Workgroup.

[Workaround]: Manually create an 'ArcSDE_License' entry as New String Value.
                     Modify and copy string from the ECP file.

Re: Failed to connect DB - Bad login user

Anonymous User — Wed, 10 Oct 2012 08:36:36 GMT

Original User: Khoda_Galyna

I have the same problem using the trial version. And when I try to download this file, I get the message: wrong authorization number. but Im sure its corect. ctrl + c, crtl + v from my e-mail.

Re: Failed to connect DB - Bad login user

GarrettMoeller — Thu, 18 Oct 2012 03:23:37 GMT

Phil,
Thanks for your suggestions.
I have created the new 'ArcSDE_License' entry as New String Value.
I successfully downloaded 'authorization.ECP'
However, this part of your suggestions I don't understand:
"Modify and copy string from the ECP file."

Best I could figure out was to open the ECP file in notepad, copy the contents,
then goto 'Modify' after right-clicking the 'ArcSDE_License' and paste it in there.
However, this didn't work.
What am I missing?
Thanks

Re: Failed to connect DB - Bad login user

Anonymous User — Thu, 18 Oct 2012 14:34:48 GMT

Original User: asrujit

Hi Garrett,

Just copy the authorization for ArcSDE for SQL Server Workgroup and paste it in the string, instead of all the contents in the ECP file.

This should work for you.

Regards,
Asrujit

Re: Failed to connect DB - Bad login user

AshleyCassol — Mon, 29 Oct 2012 16:10:27 GMT

I am having the same problem. Tried the solution " Manually create an 'ArcSDE_License' entry as New String Value.
Modify and copy string from the ECP file."

It did not work. Still getting the same error.

I'm pretty sure all my permissions are set up ok in SQL Express.

Any other suggestions ESRI??

Thanks,
Ashlie Hildebrand

Re: Failed to connect DB - Bad login user

Anonymous User — Tue, 20 Nov 2012 18:05:07 GMT

Original User: cminteer

I am having this same problem in a new Amazon instance of Server 10.1 SP1.

The default SQL Express instance in this AMI is called "MSSQLSERVER" instead of "SQLEXPRESS."

So, when I browse to 'HKEY_LOCAL_MACHINE', 'SYSTEM\CurrentControlSet\Services\' there is no MSSQL$sqlexpress. Instead, there is a 'MSSQLSERVER' - and there is already an "ArcSDE_License" key there.

I tried the suggested workaround of generating the license information from the link provided, using a valid ECP number, then creating the "ArcSDE_License" key (I renamed the old one) and entering the info.

I still get the same error.

Is ArcGIS Desktop looking specifically for a "SQLEXPRESS" instance name and registry key?

Chad Minteer
Electronic Data Solutions

Re: Failed to connect DB - Bad login user

Anonymous User — Thu, 06 Dec 2012 20:21:21 GMT

Original User: disuse

I am having the same problem. Tried the solution " Manually create an 'ArcSDE_License' entry as New String Value.
Modify and copy string from the ECP file."

It did not work. Still getting the same error.

I'm pretty sure all my permissions are set up ok in SQL Express.

Any other suggestions ESRI??

Thanks,
Ashlie Hildebrand

Just to be clear, you need to paste the entire line that starts with sdeworkgroup into the Registry. Don't try to pull anything out of the line as it's looking for the entire thing.

Once I did this, I could FINALLY create databases.

Re: Failed to connect DB - Bad login user

JustinConner — Mon, 10 Dec 2012 18:44:25 GMT

If you already have the software registered you want be able to get an authorization file emailed. So you need to navigate to C:\Program Files\ESRI\License10.1\sysgen and open keycodes.txt in notepad. You'll notice after the 3rd comma it will say "none". This is the expiration date. The bug occurs when an expiration date is not specified in the keycodes which then causes the ArcSDE_License registry key to not be created.

The workaround like mentioned before is to create that registry key, open the keycodes.txt file, copy the last line COMPLETLY (the one that begins with sdeworkgroup�??) and then paste it into the newly created registry key. Refresh your registry and open up ArcCatalog.