Latest Contributions by PaulHuffman

I thought that because I couldn't ping my SQL Server machine from my ArcDesktop client PC that I had some kind of network topology problem.  But then I found out that it was Windows Firewall policy that was blocking the ping response.  I did something like these directions for Windows 7 http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/how-to-enable-ping-response-in-windows-7/5aff5f8d-f138-4c9a-8646-5b3a99f1cae6?auth=1 to get the machine echoing ping requests. Now my desktop, my ArcServer, and my SQL server all ping each other,  but I still can't make a database connection from a client machine. ... View more

I keep pecking away at this.  Microsoft did a good job of hiding "local security settings" in Windows 2012 R2.  I couldn't find it under "Administrative tools" Error 15118: The password does not meet Windows policy requirements because it is not complex enough on my SQL machine but I found it by running secpol.msc How to Configure Security Policy Settings  .  I set "password must meet complexity requirements" to "disabled"  because I didn't know where to look up what the password requirements are.  Then on the SQL machine,  I was finally able use the Create Enterprise Database tool to create a new geodatabase with the schema owned by sde by using localhost as the instance.  Then on the other virtual machine running ArcServer, NSMAP, I was able to make a sa database connection to Orthos3 using instance NSQL.  But I was still unable to make a database connection at my desktop client.  Tried turning the Windows Firewall off on NSQL, tried instance NSQL, 192.168.3.222, NSQL\MSSQLSERVER, 192.168.3.222\MSSQLSERVER.  So I still have a network problem, I guess. ... View more

Now I have a Orthos and an Orthos2 database that were created with sequential runs of Create Enterprise Geodatabase while logged into NSQL,  but no sde user was created.  Looks like the schemas are dbo.   Desktop on NSQL can make a database connection to them as sa, but still no client machine can.  Wait, let me try lowering the firewall again.   ... View more

Yeah,  here's SSMS on the SQL machine, NSQL.  Top connection is Windows Authentication,  bottom is DB authentication using the sa account that I have been trying to use with Create Enterprise Geodatabase.  Strange thing is there is the database orthos that I was trying to create.  Did my last attempt on local host work despite the error that sde wasn't a good enough password? ... View more

That's interesting.  When I try localhost on the SQL Server machine,  I get a different error.  Looks like it connected the SQL instance. Error creating geodatabase admin user. [ERROR: Failed to create sqlserver login sde (-51).  Error: Underlying DBMS error (-51). Extended error code: (15118)  [Microsoft][SQL Server Native Client 11.0][SQL Server]Password validation failed. The password does not meet Windows policy requirements because it is not complex enough. ] I thought everybody named their sde account sde, pw sde.  Tried again with sde password SdePassword2!, but this still said it was not good enough. What does it want? Specifying the host name only, without the instance name, still didn't work on either client machine. I took a look with SSMS file logged into the SQL machine,  and I have two versions of the database that were created when I tried Create Enterprise Geodatabase while logged into the SQL machine,  Orthos and Orthos2. But looking at users,  there is no sde user.  Also the schema seems to be owned by dbo.  Maybe the tool successfully made the databases, but failed to create a sde user, so the schema had to be dbo. ... View more

The heck of it is that the DBA never really was in favor of this installation and now seems to be reluctant to help.  The last message from him was "All I did is a complete install of SQL server, and create a system administration account. The rest is up to you."  We've had a rocky relationship lately, with him accusing me of changing MySQL passwords without notifying him, and running his complaints up the COC, but the accusations have turned out to be untrue.  So if I finally find out that this SQL server was not completely implemented, and if I were a spiteful man, I might cast aspersions his way.  But I've found the best policy is generally charity and forgiveness, and I'm not even Christian. ... View more

Been trying to get a support ticket on this since last Friday.  Can't tell if it's stuck somewhere in the DOI or at ESRI. ... View more

Good idea John, but it didn't work.  Thanks. arcpy.CreateEnterpriseGeodatabase_management(database_platform="SQL_Server", instance_name="localhost/MSSQLSERVER", database_name="Orthos", account_authentication="DATABASE_AUTH", database_admin="sa", database_admin_password="1F******", sde_schema="SDE_SCHEMA", gdb_admin_name="sde", gdb_admin_password="***", tablespace_name="", authorization_file="C:\Users\Administrator\Documents\ArcGIS 10.3.1\keycodes") Runtime error  Traceback (most recent call last):   File "<string>", line 1, in <module>   File "c:\program files (x86)\arcgis\desktop10.3\arcpy\arcpy\management.py", line 4857, in CreateEnterpriseGeodatabase     raise e ExecuteError: Failure to access the DBMS server Failed to execute (CreateEnterpriseGeodatabase).  ... View more

When trying to get to my Desktop 10.3.1 install files on my network,  I discovered that Network discovery was turned off on my SQL machine, NSQL. I turned that back on, and discovered that now my client machines can ping the SQL server by IP address.  I was momentarily excited that I had found the reason that client machines couldn't run Create Enterprise Geodatabase.  but got the same result from client machines.  So I continued to install Desktop 10.3.1 on NSQL, got a desktop license over my network, installed msodbcsql on NSQL,  ran Create Enterpise Geodatabase with a keycode file pulled across my network, but I still got "Failure to access the DBMS server".  ... View more

Thanks,  Brain.  Did that previously.  ... View more

I am getting a different set of setup screens.  I've tried running this a couple times, and the last time it ran, Windows reported that it was hung and looking for a solution.  I thought that was a sign it was already installed, but I can't find anything in the apps. Should it appear under Microsoft (Hey, I have Microsoft Solitaire Collection! Where did that come from, my upgrade to Win 10?) Or should it be under S?  ... View more

I thought I could download SSMS from Download Microsoft® SQL Server® 2012 Express from Official Microsoft Download Center ,  I got SQLManagementStudio_x64_ENU.exe, but much of the install GUI seems to be for installing or repairing SQL Server. Don't think I have been able to find the correct path to install SSMS because I don't see it in my Apps.    ... View more

Thanks John.  I thought about this work around,  but even if I create the database with Desktop on the server won't client machines still be unable to make a database connection if I have an underlying network problem? ... View more

Found that the SQL Server Browser was disabled,  so I started it, and set it to automatic.  Found that the TCP/IP was enabled for all three.  But still getting "Failure to access the DBMS server Failed to execute (CreateEnterpriseGeodatabase)"   Doesn't the fact that I can't ping the SQL server host from either of my two client machines mean that I have a network problem?  Can't even ping NSQL it from the ArcServer virtual server, NSMAP, that is sitting in the same box. ... View more

1.  Tried the tool and script both from ArcDesktop on my local PC and from my ArcServer machine NSMAP. 2.  I've logged into the SQL Server machine, NSQL, and used SSMS to connect to the instance to verify the settings.  I guess there's a way to install SSMS on one of my client machines to test the connection, but I haven't tried that. 3. Don't know what that MS SQL Server browser is. How to I check that?  How do I start it? ... View more