Latest Contributions by KyleLawhorn

‎08-29-2019

The enterprise geodatabase is being built with Arc Catalog 10.2.2. There is no error message, Arc Map just closes out and sends the user to the desktop. We're trying to upgrade everyone to the 10.5 version of Arc Map. However, the project we're working on has tools designed for 10.4.1.

‎08-29-2019

I have a few users that get "blown out" or "kicked out" of Arc Map when they attempt to save their edits. We're currently using 10.4.1 in production on a SQL 2016 Database. The geodatabases are made using 10.2.2 catalog. The users that are experiencing this issue all have usernames over 12 characters. How can I rectify this?

‎07-19-2019

No. I realized my issue after I submitted the question. I signed in as the DBO and now I'm able to register it as versioned. Thanks for your help.

‎07-19-2019

I'm using Arc 10.5 (Catalog/Map) I've created my enterprise geodatabase, I've loaded data into the geodatabase, and now when I go to enable versioning the options are not able to be selected? How do I register this data as versioned?

‎04-26-2019

Hi all, I wanted to see if there was a way to create a heatmap based on time spent in a certain AOI. What I mean by this is a layer you can toggle on/off that would go from clear to red as you spend more time looking at a certain point. My reason for this is a good number of people at my company struggle to know where they've already been when we're working with large AOIs and large data sets; it can get tricky to make sure you've reviewed such a large swath of imagery. Ideally this layer would be clear but as you move around in the imagery it would make darker patches where you've been. Maybe this could be based on cursor movement; however, I don't think that's the best option. I don't actually know whether or not this is feasible but I thought I'd ask. Thanks for any help. Edit: It seems like what I'm wanting to do is possible, albeit difficult to implement. An alternative that I ended up working with is creating a grid layer that's relatively dense. Then as my users finish going over an area they mark that grid square as done. Most just make the square a color that stands out, that way they know they've covered the area.

‎04-24-2019

I don't think so. I'm currently using Arc 10.5.1

‎04-23-2019

I'm trying to connect my Arc Catalog to the SQL Server I built. It works fine until the server is turned off/restarted. Then it is unable to connect again. I get the following error message: The thing that trips me out the most is when I do "New Database Connection" in Catalog, it shows my available databases but doesn't allow me to connect. Server: Windows Server 2012 R2 w/ MS SQL 2012 SP3 Client: Windows 10, SQL Native Client & ODBC 13 Drivers. Like I said, when I first installed SQL everything worked fine, but since restarting the server to apply an update everything fails.

‎04-19-2019

There are no longer two servers. I "inherited" this role as DBA and am having to learn as I go. At the present moment I have a physical server that is running Hyper-V and that virtual server instance (In Hyper-V) is managing the SQL Server. I'm connecting to and modifying everything via Arc Catalog on my laptop locally. There isn't really anything stopping me from using the physical server itself. The only reason I'm running it virtually at the moment is the added layer of "protection" in that it's easy to create snapshots and roll back to a previous point in time if I screw something up. Once I work through these errors and get some stability to the whole effort, I could rebuild on the physical layer. Thanks, Kyle Edit: After doing some more tests, if I restart the Server, I am unable to connect to the GeoDatabase. Again, if I roll back to my snapshot it has no issues; I'm able to create and use multiple GeoDatabases.

‎04-19-2019

I wanted to bring this to your attention because it might help someone else down the line, but I'm having issues again. I was able to get it working yesterday. I completely uninstalled SQL and all the drivers, clients, etc that go along with SQL on both my server and my client. After reinstalling SQL Server 2012 with SP3, the SQL Native Client, and the OCDB 13 drivers everything worked like a charm. Not only was I able to build the geodatabase, but I was able to add data to it, connect to the database in Arc Map, and modify the data. It was working exactly as intended. Upon getting in to work this morning, I fire up Arc Catalog and I'm still able to connect in the catalog and on Arc Map. It's working well. However, this is where I run into a problem. I have the SQL Server running on a virtual machine; I shut the virtual machine down and allocated more RAM and more processors to the virtual machine. After booting back up Arc Catalog no longer wants to connect to the geodatabase and gives me the following error: Failed to connect to the database. This release of the GeoDatabase is either invalid or out of date. DBMS table not found [42S02:[Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Invalid object name "Wraith.sde.GDB_Release".][Wriath.sde.GDB_Release] Is there anything I can do to move past this error? I have checkpoint from last night when it was working, so I should be able to roll everything back to that point, but I expect I'll encounter this error again when I try to increase the performance of the virtual server. Any help is appreciated. Thanks, Kyle Quick Edit: After rolling back to checkpoint I created yesterday I am able to connect to the GeoDatabase "Wraith" in Arc Catalog.

‎04-17-2019

I installed the ODBD driver 11 and get "Failed to connect to the specified server. Do you want to continue? Failure o access the DBMS server.

‎04-17-2019

After uninstalling the OCDB driver I am unable to connect to the server via Arc Catalog. "Unable to connect to database server to retrieve database list; please verify your server name, username and password info and try again. Failure to access the DBMS server. The physical server managing the Hyper-V instance that the SQL server is running on is fine, as is the virtual SQL server. Both have network connectivity and have not had any issues so far other than this. I restarted the SQL Server instance and tried to reconnect via arc catalog and was unable to.

‎04-17-2019

I have not tried creating the geodatabase in Arc Map. I'm using Arc 10.5.1 across the entire suite of products. The SQL Server is running SQL 2012 SP3. My client machine has Arc Catalog 10.5.1 the SQL Native Client, and the MS ODBC Driver 13.

‎04-17-2019

Robert, I've encountered another issue. It was working yesterday, but as of lunch time today I'm unable to get a connection to the database in Arc Catalog. I'm greeted with the following error: Failed to connect to the specified server. Do you want to continue? This release of the GeoDatabase is either invalid or out of date. DBMS table not found [42S02:[Microsoft[ODBC Driver 13 for SQL Server][SQL Server] Invalid object name 'SpartanSDE.sde.GDB_Release'.][SpartanSDE.sde.GDB_Release] If I try to create a new enterprise geodatabase I get the same error that I got when I made this thread initially.

‎04-16-2019

Yes! It worked perfectly. Thanks so much for your help, I really appreciate it.

‎04-15-2019

I'm downloading SP3 now and I'll check to see if that works. I currently have the SQL 2012 Native Client installed on my local machine. Is that the correct configuration? Thank you for your help.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by KyleLawhorn

Re: Users with long names crashing arc map when saving

Users with long names crashing arc map when saving

Re: Why Can't I Enable Versioning?

Why Can't I Enable Versioning?

Dynamic Heatmap Creation

Re: Unable To Connect To SQL Server

Unable To Connect To SQL Server

Re: Issues creating Enterprise Geodatabase

Re: Issues creating Enterprise Geodatabase

Re: Issues creating Enterprise Geodatabase

Re: Issues creating Enterprise Geodatabase

Re: Issues creating Enterprise Geodatabase

Re: Issues creating Enterprise Geodatabase

Re: Issues creating Enterprise Geodatabase

Re: Issues creating Enterprise Geodatabase