POST
|
We have an enterprise license and numerous users. Yesterday, I disconnected some users/locks on feature datasets I needed to add new features to. I unchecked the "Geodatabase is accepting connections" box, made my changes and rechecked the accepting connections box. After that, everyone's map had broken links, including ArcGIS Pro. The server was re-started last evening to see if this would fix the issue. It didn't. The users can repair their data sources, but once they save and close the maps upon re-opening, the links are broken again. Others are reporting that they can't open the mxd's at all. Any suggestions?
... View more
08-07-2020
11:51 AM
|
0
|
1
|
664
|
POST
|
It turns out that it was an old login-when I was using a laptop that I rarely use, it let me delete it there. Thanks for your help!
... View more
06-13-2016
08:12 AM
|
0
|
0
|
1050
|
POST
|
Yes, SQL server 2012, Enterprise SDE, 10.2.2, Desktop 10.3
... View more
06-10-2016
11:32 AM
|
0
|
0
|
1050
|
POST
|
06-10-2016
11:18 AM
|
0
|
4
|
3839
|
POST
|
Hello, I am trying to help our police department set up maps where they can see crime and crash data hotspots and where these may overlap. My question is this: What have those of you who have set up similar scenarios seen as the most useful way to collect/import/display this data? I am trying to avoid the trial and error phase of this, and any help or advice you can give me would be great! Here is some information on what kind of data I am looking at: The police crash RMS database seems to have one large table that encompasses many smaller tables. The data in the large table has good information in it, but no coordinates. On the GIS side, I have a road feature which has road names and right and left address ranges, and I am hoping someone way smarter than I can shed some light on somehow linking the crash table and street tables together. Thanks in advance! Robin
... View more
08-02-2013
01:25 PM
|
0
|
0
|
2054
|
POST
|
Earlier this morning, I posted and reconciled some edits from another user. When the user tried to pull down the newest version, she received an error saying "Underlying DBMS error Microsoft OLE DB Provider for SQL Server: Violation of Primary Key constraint' a85_rowid_ix1". "Cannot insert duplicate key". The table that the error referred to has one user input field asking for an installation date. There is no primary key duplication possible. I tried posting and reconciling from her version and got the same error. I tried removing the layer and still got the error. In another instance, this afternoon I was told some addresses were missing from parcels that I know have addresses. The parcel layer is joined to another table that is used strictly for the addresses. When I looked in the joined table, the addresses were not there. I started re-entering the addresses, saving edits after each one, but about the 10th address I entered I got the same error as above. This was not in a version and I have administration rights. Then the addresses appeared again. What is going on? I am using 10.1 desktop and Windows 7. Am I missing some basic issue? Or is this an IS problem?
... View more
04-01-2013
03:02 PM
|
0
|
1
|
1031
|
POST
|
In the ArcPad Data Manager tool the second to last screen has a toggle button to "Validate feature classes prior to check out"....have you tried turning this feature off? Brett, Thanks for your response, I tried your suggestion and it exported "successfully" but when I open up the ArcPad device and look at the map, the preview shows correctly, but when I open the map, only about half of our signs show up. I don't understand this.
... View more
10-23-2012
02:14 PM
|
0
|
0
|
353
|
POST
|
Hello, We have purchased Mesa units for our street department to upgrade the street signs. Initially, when we started this project, we were running ArcMap 9.3. This seemed to work fine when we tested it, but then we upgraded to 10.0. We have had problems trying to export the data to ArcMap ever since. Errors for the attribute tables were preventing us from exporting the data. We would fix one group of errors, re-try the export, and have a totally new set of errors. The last time we attempted this, the error said that the data we were working with would not accept NULL values and that the <NULL> was too many characters for the field. We were told by ESRI Support to try doing a Field calculation to have the fields take NULL values. This seemed ridiculous, so we shelved the problem for the time being. Now, we have upgraded to 10.1 with the hope that this version would work better. Now when I try to export the data, it won't let me select the signs layer for export. What am I doing wrong? Thanks
... View more
10-23-2012
07:26 AM
|
0
|
3
|
1730
|
Online Status |
Offline
|
Date Last Visited |
01-10-2024
05:59 PM
|