Thường thì việc kích hoạt bản quyền ArcGIS là một vấn đề đau đầu, hoặc sau khi sử dụng nó bị ngừng hoạt động và có vẻ như yêu cầu cài đặt lại vì không thể đọc được. Đây là quy trình bình thường để kích hoạt nó: Kích hoạt giấy phép Giấy phép có thể được kích hoạt thông qua một tập tin rời rạc hoặc thông qua một dịch vụ, cách đơn giản nhất để kích hoạt dịch vụ là: 1. Chạy công cụ cấp phép Đối với điều này bạn bắt đầu / chương trình / arcGIS / quản lý giấy phép / công cụ quản lý giấy phép 2. Trong bảng dịch vụ / tệp giấy phép, hãy chọn tùy chọn “sử dụng dịch vụ”  3. Trong nhãn dịch vụ cấu hình, tìm đích của các tệp lmgrd.exe, license.dat, sau đó lưu tùy chọn bằng nút “lưu dịch vụ” (Tệp .dat này là tệp có tên của thiết bị được cấp phép được định cấu hình ) 4. Kích hoạt dịch vụ, bạn vào nhãn “start / stop / reread”, nhấp vào “Arcgis License manager”, sau đó vào “start server”. Sau một vài giây, nó sẽ xuất hiện như đã được kích hoạt. Các vấn đề thường xuyên Nhiều khi ở trong tùy chọn này, giấy phép không được kích hoạt, thông báo “bắt đầu không thành công” xuất hiện hoặc sau một vài tháng sử dụng nó, thông báo báng bổ xuất hiện: “Cung cấp cho quản trị viên máy chủ cấp phép của bạn thông tin sau: Không thể kết nối với máy chủ cấp phép, máy chủ (lmgrd) chưa bắt đầu, hoặc sai cổng @ host hoặc tệp giấy phép đang được sử dụng, hoặc cổng hoặc tên máy chủ trong tệp giấy phép đã được thay đổi. Tính năng: ARC / INFO, tên máy chủ, đường dẫn giấy phép, lỗi flexIM: -15,10. Lỗi hệ thống: 10061 Winock: kết nối bị từ chối ” Cách dễ nhất để kích hoạt nó là bằng cách: [Sociallocker] home / bảng điều khiển / công cụ hành chính / dịch vụ sau đó bạn tìm một dịch vụ có tên là "Trình quản lý giấy phép ArcGIS", bạn chọn nó và kích hoạt nó bằng biểu tượng "kích hoạt dịch vụ", nếu nó có vẻ được kích hoạt, bạn làm điều đó với biểu tượng "khởi động lại dịch vụ" [/ Sociallocker] Nhà văn, nhà nghiên cứu, chuyên gia về Mô hình quản lý đất đai. Ông đã tham gia vào việc hình thành và triển khai các mô hình như: Hệ thống quản lý tài sản quốc gia SINAP ở Honduras, Mô hình quản lý các thành phố chung ở Honduras, Mô hình tổng hợp quản lý địa chính - đăng ký ở Nicaragua, Hệ thống quản lý lãnh thổ SAT ở Colombia . Biên tập viên của blog kiến thức Geofumadas từ năm 2007 và là người tạo ra Học viện AulaGEO bao gồm hơn 100 khóa học về các chủ đề GIS - CAD - BIM - Digital Twins. Getting the version of the geodatabase and RDBMS would be most helpful for any potential troubleshooting. Have your admin query the SDE_version table and return the info for the geodatabase side. --- George T. We support PostgreSQL also and have had many clients move that direction. --- George T. Hello, my organization is experiencing the same error. However, we do have sql server 19 and our geodatabase is at version 11.1. We have ran the diagnose version tables and metadata tables and no errors are reported, however the error message regarding state_id=0 in ArcGIS Pro 3.2 persists. We dont have any other versions aside from default. Any recommendations on how we might fix this? I am not sure of a specific recommendation. It may be best to contact Technical Support and work with an analyst on this issue. --- George T. We also exp. same things with ArcGIS Pro SDK, randomly showing errors , worked fine ArcGIS Pro 3.1 , broken in 3.2 For that reason we rollback to ArcGIS 3.1 ; we have geodatabase / sql server that compatible so we shoulnd't mess with it. hello all, I just wanted to add a note here. Drawing Alert is a new feature for ArcGIS Pro 3.2. Drawing alerts—ArcGIS Pro | Documentation The purpose of this feature is to bring up any issue that Pro internally runs into while drawing layers in the current map extent. Prior to 3.2, these alerts (warnings or errors) were getting ignored and never made the users be aware of these. With this new feature, now you can be aware of any potential issues in your map's current extent... which used to get unnoticed in previous release. Therefore, going back to 3.1 or previous releases is not really solving any problems except that they get hidden away. Please let me know if you have any questions. @TanuHoque In our case, once we got "Drawing error" , geometry was disappearing. now we do believe we have compatible geodatabase and versioned table that worked for decades -so what is the "hidden away" issue ? -was there mandatory geodatabase upgrade to 11.2 ? - it's simple , it worked fine 2.x, 3.1 and suddenly broken in 3.2. without clear reason - i will create support ticket but we need clear guideline on this , as i suspect other will experience same issues Thanks Same in my case, the geometry completely disappears after the error. Although these drawing errors being displayed are supposed to be a feature of 3.2, I find it fishy that this specific error is happening to others all while nothing appears to be wrong with our databases according to ESRIs own diagnostic tools (diagnose version metadata and diagnose version tables). ArcGIS Pro 3.2 introduced discarding and undoing edits on non-versioned data which makes me wonder if there was a bug introduced. Currently, this issue isn't documented as a bug, and when we opened up a support ticket, support seems hesitant to do so because they can't recreate the issue. Altogether, I think either there is truly something wrong with our databases that the diagnostic tools currently don't catch and we have been fortunate enough to not to receive this error in every previous version of ArcGIS Pro or there is some issue with ArcGIS pro 3.2, which seems more likely to me. As of now, I will probably just revert back to ArcGIS pro 3.1. I was having this same issue using 3.2 with the drawing errors and the geometry disappearing. Everything would be normal until I started editing and split a line feature but discarded the edit. At that point I would start seeing the notices and the geometry would stop drawing. I discovered that there is a new option introduced in 3.2 to "Enable and disable editing from the Edit tab" in either a single or multiple (the default) workspace edit session. If I set this to single, hit the Edit button, and select my editing workspace, as soon as I panned and zoomed around I would start seeing the drawing alerts even though everything was still drawing and I had not made any edits yet. These alerts would continuously open and close as I panned around, but the geometry for all of my layers continued to draw. Even if I split a feature and hit the Discard button the geometry did not disappear as it did before. As soon as uncheck the Edit button the drawing errors would stop. However, if I set the editing option to "Multiple workspace edit session", then split and discard the edit, the geometry would again disappear and the notifications would begin to pop up again. TLDR: Enabling the Editing option "Enable and disable editing from the Edit tab" with single workspace edit session should keep the geometry from disappearing. Hi ESRI, Based on feedback on Drawing Error newly introduced issues in this forum is that this issue started happen in a newer version ArcGIS Pro 3.2 that was not present in previous releases, and it necessitates a workaround, it can indeed be classified as a bug. Users can workaround it , but if we need supports hundreds of users, then this will be raised as lots of supports. Result of this issues is to rollback to ArcGIS Pro 3.1 at this moment What i am hoping is that this being replicated properly by ESRI and have Patch on this . We were looking forward to have 3.2 with some other bug fixes and enhancement Thanks Thanks for this work around. It keeps our geometry from disappearing during an edit session. Reminds me of how we used to start an Edit session in ArcMap. Kind of annoying that we have to do this work around just to keep our data on the screen during an edit session. One of the things that I liked about Pro vs ArcMap was not having to start an edit session and being able to edit from multiple workspaces at once. 3.2 went backwards with this bug. @PeteJordan yes, of course. I agree. If the solution is upgrade your database or something; and the meanwhile the best option is to roll back - that is the right thing to do. My point was (aside for cases like your) that roll back will only hide those errors as Pro had no such options to bring up error messages/alerts to the users in previous releases. @joonpark Thanks for opening a support ticket. I hope they will provide you a resolution soon. The goal of this new Drawing Alerts capability is to surface up any warning/error that a layer throws while drawing. In previous releases, that was getting eaten away -- we never made the user be aware of that. Now Pro does bubble it up if something goes wrong. This tool is not meant for you to help you investigate and finally resolve this issue. It is only to show a notification. Imagine we didn't have this Drawing Alerts option in 3.2, and due to upgrade or version incompatibility etc., geometries were not drawing... and imagine you have a lot of layers and features drawn in your map... it was very likely 'missing geometries' might have gone unnoticed. Now with this Drawing Alerts, Pro tells you that there were some issues it ran into while drawing those layers/features. Hope this helps. I went ahead and started a ticket on this as well, to make someone look at this on screen share. I am using enterprise databases on SQL Server 2016, geodatabase version 10.5.1 (to keep them open for ArcMap until some time next year). I only noticed drawing alerts in Arc Pro 3.2, with the same error text “Target state not found in the States table (STATE_ID = 0),” and with this error, geometry (but not labels?) disappears for all features in that geodatabase. I am using multiversioned editing mode, because I am cutting features from a file geodatabase and pasting to an enterprise geodatabase. The error stream and disappearance seem to happen when there are other users connected to the EGDB, so there are multiple states in the SDE_states table. Looking at the SDE_states table in SQL Server Manager, there is definitely a State_ID value of 0 along with other values in the State_ID field. I have done this kind of editing through the earliest versions of Arc Pro 2 (roughly in 2018 or 19), and earlier in Arc Map 10.5 and 10.7, with very few errors in the editing process, drawing or otherwise. This is buggy behavior and not brought about by "corruption in the database", so let's hope it gets looked at as such. |
