POST
|
Hi All, Tentatively - At long last it appears we have an answer to this situation. What appears to have been the issue all along is a problem with the ArcGIS Desktop installation on the individual workstation PC's. Not with the database / ArcSDE side of things at all. What we found is that when we installed ArcGIS Desktop 10.5.1 on a PC that had never had ArcGIS on it before, it had *no* performance issues. When we loaded an mxd from a PC plagued with the slowness onto the new PC - we had no issues with slowness. So - on the PC's with the degraded performance in ArcMAP. Their ArcGIS Desktop upgrade path has been as follows. 10 -> 10.1 -> 10.3 -> 10.31 -> 10.5 -> 10.51. When we upgraded to 10.5 we first saw this issue. All along the way we've simply ran the uninstallation / installation process as usual. But this has left some old folders from those previous installations in place. On the Affected PC's - what we did was to uninstall 10.5.1 completely. *THEN* we went though the folder structures on each PC and manually deleted *ALL* folders to do with ArcGIS. Every single one. Completely blow them away. This is what I remember finding on my pc. You want them all *GONE*. Program Files(x86)\ArcGIS Program Files(x86)\Common\ArcGIS *your username*\Appdata\Local *all ArcGIS folders* *your username*\MyDocuments *all ArcGIS folders* We had folders left over from 10.1...10.3 etc etc etc in those locations. Only when we deleted all those then installed ArcGIS Desktop 10.5.1 again did our slowness problems go away. Simply Uninstalling 10.5.1 then reinstalling it did not work. Only when we deleted all those old folders did we get our performance back in ArcMAP. We've only just found this. Time will tell if our ArcMAP performance remains where it should.
... View more
08-02-2017
01:35 AM
|
4
|
4
|
846
|
POST
|
Apologies for the late reply. Yes we've done much of the troubleshooting in whilst in contact with technical support, and we most certainly have a case logged with them. They have actually been very good with getting onto the situation, albeit without result. Kory: Thanks for those links and the heads up. I will keep an eye on those situations as well. It's very possible they could well be linked with what we're experiencing. For a particular MXD - if we copy all the feature classes it uses from SDE into a locally stored file geodatabase - then yes the slowness *does* go away. So far as we've tested anyhow. But we have a number of officers editing versioned feature classes so that gets a little frustrating / time consuming to manage. Minott: Our issues do sound very similar to yours. We are also of the opinion now there's a bug / issue somewhere with 10.5 over 10.3 (that we moved up from). Our support case is still being nutted through - we know of at least one other similar issue in Australia. But nothing new I'm sorry to say.
... View more
03-27-2017
05:42 PM
|
0
|
1
|
1142
|
POST
|
The issues are still *not* fully resolved unfortunately no. The issues I spoke about with SQL above *were* having an impact in certain situations - and with certain operations - but it does not appear to be the full picture. Fixing the nvarchar(max) instances in SQL - as well as completely reworking all the indexes - has *not* fully solved the sluggish ArcMAP performance. We ended up getting a SQL tech in to go through our SQL setup with a fine tooth comb. He found a few minor things - but nothing that has made the ArcMAP issue go away. We've seen a minor improvement it must be said. So... although all of that has helped - the sluggish ArcMAP issue remains. We really see it when switching layers on and off, zooming in and out, and when we put scale dependencies on labels etc etc. Also when saving edits, this really takes a long time now. We then hit upon building feature caches in ArcMap to aid with zooming in and out - which also *does* help with reducing draw times when working in ArcMAP. So that helps. But switching the layers on & off still takes ages. We really see a difference now with scale dependencies - where features or labels switch off at certain scales etc. This seems to make things very slow. Much more so than previously. We did also hit upon a suspicion that datasets switched over to high precision under 10.3 weren't so happy in 10.5. No real concrete evidence for this but nevertheless we re-did this under 10.5 to tick that box. We also made sure our SQL box wasn't maxing memory and killing the machine's performance or anything like that. So - we feel we've chipped away at the problem as much as we can - and improved things a small amount - but we feel now the remaining issue is a bug with ArcMAP. Arc Catalog seems completely fine and responsive like you'd expect. We did have an issue sometimes with Arc Catalog where it would go crazy - creating 10 tabs in the windows task bar and flickering our screens like mad. Fixing the nvarchar issue, the indexes, and the high precision issue (only suspected) and making Arc Catalog happy seems to have stopped this from happening. That first appeared under 10.3 and originally didn't seem to have any effect beyond the flickering screen for a few minutes. We suspect now it was probably due to issues we had with our setup at 10.3 - but which really didn't affect things then. At 10.5 those issues *did* come home to roost. So - no silver bullet I'm afraid. But hopefully that helps somewhat.
... View more
03-17-2017
02:07 AM
|
1
|
3
|
1142
|
POST
|
Yes ok Dan I will do that once we have properly verified the outcome.
... View more
02-27-2017
07:23 PM
|
0
|
1
|
1142
|
POST
|
Some findings. This is at the limit of my knowledge so I will describe it as best I can. ESRI Australia have identified what looks like a bug with ArcGIS 10.5 and SQL 2012. The issue is around the indexing of nvarchar (max) fields in SQL. So - fields that are set with nvarchar (max) in SQL are causing problems in ArcGIS - because ArcGIS can't index them properly...... resulting in very poor performance. If in SQL you change the nvarchar(max) definition to nvarchar(254) - the issues disappear. The way we tested things was choosing a feature class with say 10,000 records in Arc Catalog and try and sort on any of the fields. If you have nvarchar(max) set in SQL - this took a *very* long time. Set to nvarchar(254) and the sorting was back to around 10-15 seconds as usual. After we have made the changes in SQL to all our datasets (a days work) - I will report back if the poor performance issues have indeed disappeared. Initial testing though seems promising. Hope that makes sense. The nitty gritty of databases isn't my forte.
... View more
02-27-2017
07:15 PM
|
3
|
1
|
1142
|
POST
|
Yes I have several ArcMAP mxd's made under 10.3 (or earlier) that are taking a very long time to load now under 10.5. 10 minutes plus for me as well. Re-making the mxd's under 10.5 does help. It at least allows the projects to load in a decent timeframe - but they still suffer very sluggish performance when doing simple tasks. If I find any information that helps, I will certainly post it here.
... View more
02-22-2017
04:41 PM
|
0
|
1
|
2153
|
POST
|
ESRI Support have told us that other people are also suffering performance degradation in ArcMap after upgrading to 10.5. It's *really* affecting the amount of work we can get through daily. Just wondering if others with this issue can voice it here to build a case for some action on it. Also to judge how widespread this issue might be.
... View more
02-22-2017
12:03 AM
|
2
|
3
|
2153
|
POST
|
Thanks for the reply Jayanta. Yes I've tried renaming the ArcMap normal.mxt and creating a new template - no change. I tried doing a complete application profile reset as per your link - no change. I can confirm we have installed service pack 3 for SQL Server 2012, and have indeed upgraded our enterprise geodatabase. We have also re-done all the indexes. What we've also discovered is that if we load 1 - 2 feature classes into ArcMap - it's ok. If we load more than that, we start seeing the slowdowns I mentioned above. Also, we've found that when we sort large-ish datasets in Arc Catalog (16,000 records for example) by ObjectID - or anything - it takes a long time. Far longer than it did under 10.3. At this point - it seems to be something to do with larger amounts of data. Either ArcMap projects loaded with several layers or operations on large-ish datasets. Just viewing a single large dataset in ArcCatalog - no problem.
... View more
02-20-2017
11:44 PM
|
1
|
1
|
2153
|
POST
|
Hello All, We have just updated from ArcGIS 10.3 to ArcGIS 10.5. Suffering from very slow performance in ArcMAP now with certain things. I've completely re-made MXD's from scratch under 10.5 that I had under 10.3 to remove possible changeover issues. When I simply tick on/off layers it takes a long time (1 minute or more) to update the display or give me control of ArcMap back. When I save edits - long time to do that (2 minutes or more) When I change a layer from editable to not editable - long time (1 minute) to do that. I'd have maybe 10 layers in the MXD with JPEG 2000 aerial photo loaded in - but not displayed. Arc Catalog displays layers quickly - as you'd expect. Loading one or 2 layers into ArcMAP also seems ok. But more than that *really* seems to slow it down. I never had extremely slow responses like this under 10.3. We're putting in a support call but just wondering if anyone else has noticed this - and might know what the cause is. Data sits in SQL 2012 with ARCSDE.
... View more
02-19-2017
09:27 PM
|
4
|
61
|
43551
|
POST
|
This issue ended up being none other than misaligned print heads on the HP Z6200 printer. One of the heads were misaligned, while the rest were not. This is why only some content was fuzzy or ghosted while other content was not. The colours requiring the use of the misaligned print head came out bad - while everything else was good. I simply performed a print head alignment on the printer and my map came out crystal clear after that.
... View more
07-16-2015
08:13 PM
|
1
|
1
|
861
|
POST
|
Hi Sephe, it certainly seems to be pointing toward the printer with all things considered I agree. The printer has 1.5GB RAM and a 160GB HDD. We had the previous/older model Z6100 printer and never had any issues like this. The Z6200 has better specs so...... confusing upon first thoughts. Unfortunately I don't have another printer with the same abilities that I can use for a comparison. However, the lesser-able Océ Colorwave printer I *do* have does not display the same issues, but can't get the print job to the standard I need. If there's a halftone setting etc etc that I'm missing perhaps? It's well hidden if it does exist.
... View more
06-21-2015
11:42 PM
|
0
|
1
|
861
|
POST
|
Hi Robert, Thanks for your reply. In this instance, I am trying to print an A0 sized map onto HP Heavyweight Coated paper with an HP Designjet Z6200 printer. The printer also has a Post Scipt upgrade installed. A few things in addition: I can create crystal clear PDF's or TIFF images from my ARCMAP session without issue. When I view those onscreen they appear clean and fuzz free. But if I try and *print* those images - I get the described issues happening. Or If I print straight from my ArcMap project I get the fuzzing issues happening. The very odd thing is that some annotation classes appear fine when printed, yet others print out terribly. I've also noticed that some polygon layers are printing with a very grainy appearance as well, yet others are smooth and clear as I'd expect. So I've tried a raft of printer driver changes, tweaks, and updates - but all to no avail so far. It really looks as if the features affected are printing at an extremely low or downgraded resolution for some reason. I will check the Anti Aliasing settings though and see if that helps.
... View more
06-21-2015
05:48 PM
|
0
|
1
|
861
|
POST
|
Thanks Dan for putting me in the right area. I admit though I *vastly* prefer the more classic forum layout. Have tried exporting the map to PDF. However when I did that I got additional symbology corruption. For instance - I had a polyline layer on the map symbolised with a dotted and dashed line. Exported to PDF this became a weird mix of solid line with random breaks. The annotation still appeared low quality as well. In addition, some polyline layers appeared fuzzy as well. At this stage I think I will need to re-create the map from scratch without any transparency from the get-go and see where I end up. Interestingly - when I print this map to our lower quality CAD printer (OCE colorwave 600) then I *don't* get any fuzzy linework or annotation. But the printout is too low quality for what I need. The information I read at the moment is that if you have a rasterized layer - or transparent layers in your maps then you can suffer pixelisation of other layers. Sometimes you can increase your halftone quality settings to help the issue - but that isn't an option I seem to have. You can put transparent layers as low down the order as possible on the map - but again no dice for me. Frustrating.
... View more
06-15-2015
05:53 PM
|
0
|
1
|
861
|
POST
|
Hi All, I have ArcGIS ver 10.1. I have a map with annotation labels in it, and some of them are printing at a very low resolution or are appearing very fuzzy in the printout. Cannot for the life of me figure out what is going wrong here. Am using an HP Designjet Z6200 60inch printer. Simply bumping up print setings does not solve the issue. Looking very closely, it almost appears as if the badly printed annotation has some type of dropshadow or ghosting going on. Reading on the web - I came across some information regarding halftone settings for printing, but this wasn't clearly explained and I'm none the wiser at this point. I also came across information that suggested transparent layers could be to blame. My map *was* full of transparent layers - so I took all these out and replaced all transparent stuff with solid colours. No Dice. I have Aerial imagery which I want to fade into the background around the map. Then in the middle I have the Feature Classes etc etc making up the map. First I tried making the imagery itself transparent. Works a treat onscreen - but is that causing the annotation issue? Then I tried putting a mask over the imagery and fading that. All no dice. If I can just get readable annotation then I'll be happy.
... View more
06-15-2015
01:42 AM
|
0
|
10
|
4495
|
POST
|
Hi David. Am interested in what you found about your editors copying data from spreadsheets causing the duplicate primary key errors. This is something we theorized could be happening in our situation, but our errors weren't consistent enough to confirm or disprove. I admit though that I still can't fathom how copying data into attribute fields from spreadsheets could cause database primary key errors. Could you elaborate?
... View more
08-21-2014
07:01 PM
|
0
|
1
|
593
|
Title | Kudos | Posted |
---|---|---|
1 | 03-17-2017 02:07 AM | |
1 | 07-16-2015 08:13 PM | |
4 | 02-19-2017 09:27 PM | |
1 | 02-20-2017 11:44 PM | |
3 | 02-27-2017 07:15 PM |
Online Status |
Offline
|
Date Last Visited |
01-17-2021
10:05 PM
|