POST
|
I thought I recently had a problem like this. I found it. I found out that outside ArcDesktop I had to also explicitly check out extensions. https://community.esri.com/thread/219120-why-doesnt-sa-slope-get-called-as-expected-in-python-script
... View more
04-15-2019
03:39 PM
|
0
|
0
|
32
|
POST
|
How do the python script lines run in a python window in ArcDesktop or Pro? I wonder if you might need to implicitly call the python library with import arcpy to run in python outside of an ESRI environment. Did your python IDE throw any error messages?
... View more
04-15-2019
03:31 PM
|
0
|
2
|
32
|
POST
|
I went into SSMS, added the windows login for Adrianne to the sysadmin role. And it looks like my network and database administrator is already in that role. I didn't find this role at the database level, I found it at the Server Level Security>Server Roles. Then for testing I made a Windows user account on a PC on the network for Adrianne, then logged in as Adrianne, opened ArcCatalog, made an OS connection to a couple databases as Adrianne, checked Administration> Add User and it wasn't grayed out, so I think it is working. I didn't have another user handy to try to add but this test seems to show this will work.
... View more
04-12-2019
10:26 AM
|
0
|
0
|
68
|
POST
|
Yes, this is a known bug. https://support.esri.com/en/bugs/nimbus/TklNMDgyNjc2 It could turn up with other tools and Arcpy functions and also with /t. Capitalize these if you can. Thanks to Miguel at ESRI Support.
... View more
04-08-2019
03:00 PM
|
0
|
1
|
33
|
POST
|
I was just working with Miguel at ESRI tech support who was amazed at this behavior on my server, and then was able to get the same kind of error using the Create Database User tool on his end with both Arc Catalog 10.5 and 10.6.1 when the user name started with n. Do you think there is a way to escape out of the \n combination in the domain user name when using ArcCatalog >Administration>Add User>Create Database User? I was able to use SSMS to add this ykfp\nrom*** login to my instance, geodatabases and roles, but I was hoping that tomorrow I could demonstrate a simple workflow on how to add users and privileges using ArcDesktop tools to a fairly new employee that I want to take over as administrator for me soon.
... View more
04-04-2019
03:29 PM
|
0
|
1
|
33
|
POST
|
I had this happen when I was adding two new employees to my geodatabases with their OS logins from our Windows domain, using ArcCatalog 10.6.1 and the Administration> Add User workflow. The first guy went easy, the next guy didn't work. His domain login is ykfp/nrom***. The error message made us wonder if /n is getting read as a line feed and if I needed to escape this with quotes or something. There must have been other places where someone had a domain name that included /n however, so it seems unlikely that I am the first to encounter this. I also tried the other syntax for his domain name nrom***@KFO.local. Dropbox - AddingnromeroEd.png Yesterday, I successfully added ykfp\Nrom*** as a user to one geodatabase. But my domain manager had given me ykfp\nrom*** as the login. I haven't heard back from the domain manager when I asked him to check on the capitalization. Does capitalization matter in Windows OS authentication? I don't have a way to test this to see if it will work for the user. I can't make an account on a PC in the domain as this user to try the geodatabase connection as ykfp\Nrom*** because I don't know the user's password. Tomorrow, I plan to be in the user's office where I hope to work with him to install Desktop and add his geodatabase connections.
... View more
04-04-2019
12:50 PM
|
0
|
5
|
183
|
POST
|
The database administrator in this office just told me that he would prefer that I not create any more DB accounts but to do this with existing OS user accounts, that we create a small group of OS user accounts to be the Database Administrators. At first, I was resistant to this because I was taught in my ESRI class that the standard practice was to create headless DB accounts to be Database administrator, geodatabase administrator, and data owner. Then I had in my ArcCatalog three different database connections, one for each level. But I think it might work OK to create a role for each to these three levels, then add to these roles any current headless DB account I've been using as well as the Windows OS user accounts that is going to take this over from me. We could add and remove Windows user accounts to these roles as people came and went. Then, I guess, the small group of users that would have these admin capabilities would just need one database connection in ArcCatalog to each of the five geodatabases, and would be able to do the sa, sde, and data owner stuff from that one connection. Would this approach work? I'm kind of worried that the data owner might look different depending on which OS user in the data owner role loaded the data. Would another user in the data owner role be able to manage privileges to data they didn't load? Might this be a case where it is simpler to use a headless DB user to load and own all the data? Like this scenario: I add myself and Adrianne to the data owner group with our perspective Windows OS domain logins. I add a bunch of data. I leave the organization, so the network admin removes my domain account. Now Bob joins the office. Will Adrianne, as part of the data owner role, be able to give Bob privileges to data I loaded?
... View more
03-28-2019
04:09 PM
|
0
|
2
|
68
|
POST
|
I got an error trying to use the Create Database User tool in Desktop 10.6.1. [Microsoft][ODBC Driver 13 for SQL Server] [SQL Server] Cannot use the special principal 'sa'. Is it not recommended to create a user "sa" to be the database owner with sysadmin priviledges? Or should I use SSMS to create this user "sa"?
... View more
03-28-2019
10:55 AM
|
0
|
4
|
68
|
POST
|
I took a look at my settings with SSMS. I wanted to create a new DB account to take over as the database owner, but I found there already is a user dbo with the login name of my OS login. So it is potentially confusing to admins after me, because it looks like dbo is the expected practice. Maybe I'll name the new DB user account "DBOwner" to give System Administrator privileges. My class textbook from "Deploying and Maintaining a Multiuser Geodatabase" used "sa" as the account name for the database owner. Maybe I'll go with that.
... View more
03-28-2019
10:25 AM
|
0
|
6
|
68
|
POST
|
I have five enterprise geodatabases in ArcServer 10.6.1 and SQL Server that I created with the Create Enterprise Geodatabase tool from my domain login, so the Database Admin account is my OS account on my local domain. But when I retire in a couple months, how can I pass this Databasee Admin authority to my successor admin? Did I screw up? Because right now I can't figure out the best way to hand this off. Will I need to leave my account on the domain so the new admin will have to add my domain login to her PC and have to switch to my user account to use ArcCatalog to do the admin on these geodatabases, like add users, create roles, add users to roles? Or can the new admin use SSMS to manage database users? But I can't remember SSMS can use my admin credentials from a PC logged into the domain with someone else's credentials. But at least I have headless DB accounts for the data owner and the geodatabase administrator account.
... View more
03-22-2019
03:47 PM
|
0
|
8
|
810
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|