Failed to connect DB - Bad login user

[MaximSpikin]

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]

[LaurynasGedminas]

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

[Anonymous User]

Original User: wpgis5673

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

[PhillipWaldron]

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

[Anonymous User]

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]

[PhillipWaldron]

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.

[Anonymous User]

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.

[GarrettMoeller]

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

[Anonymous User]

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

[AshleyCassol]

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