Latest Contributions by KevinHibma

Thank you for the information Daniel. That's the first time in this thread that has been brought up (ArcFM being installed). Looking through our system, I found this logged as  NIM096880. We do not currently have a fix, but is something we're investigating. ... View more

I'd have to see the script to determine what the exact issue is - but this reminds me of a possible issue thats fixed in 10.2. When publishing a script, all the references are looked at and scanned to see what data is required to publish. Some scripts, depending on how and what they referenced could get into a lot of python files and the hang you see is just the system being busy (hard at work inspecting) and eventually it'll come back. Or it could be an endless loop, which wont ever come back --its hard to know whats happening here. In short, if you're able to upgrade, I'd expect the problem would go away. If you can't upgrade, I'd check 1) for if you have any variables in your script pointing at folders -- if you do, whats in them. Try to clean that code up if possible. Otherwise you can post your script and I'll try to point out anything that might be causing this. ... View more

This isn't exactly the most straight forward GP Service. [a service that makes a service] It can be done, but there are some gotchas. First, it would be good to have the exact error message, second, I'd post your script. From the error you mention, its possible the GIS Server connection file (.ags) cannot be found. When creating your script, I'd have a folder of all the important pieces to this workflow. Inside that folder, I'd persist a .ags file with publisher credentials saved. Inside your script, you should be pointing at that folder / connection file. I'd also register that folder with the datastore. When you publish, the service should still have a reference to that folder / connection file and be able to access/use it. ... View more

Please post some more information: -the exact error message (turn message level to INFO at the gp service level and run it again from Desktop to get the error messages -possibly post your script -have you registered your MXD folder with the datastore? You dont have to, but in this case its probably a good idea. ... View more

Zack, This should be the model you're looking for: http://www.arcgis.com/home/item.html?id=2b6872972cec47d1ba763859a23a77e1‌ ... View more

Antonio, We'll meet in the middle I just looked up when we installed it, and it seems we installed it at 10.2.1, not 10.2.2 like I thought. ... View more

Hi Kevin, is that option for importing layer files (*.lyr) 100% compatible, and especially will the display of all feature symbolization and feature labelling be 100% the same in both ArcGIS for Desktop and Pro? It is a real nightmare for cartographers to have to redesign loads of layer files, so it is vital to have truly good compatibility and transfer of properties to the maximum extent possible. Marco, I don't have that detailed information. You best way to get these questions answered is to: 1) Get involved in the beta (with the links posted previously) 2) Direct Pro specific questions to the Pro beta forums. ... View more

Very close, try this         myPassword = arcpy.Parameter(             displayName="Hide this!",             name="hide_password",             datatype="String Hidden",             parameterType="Required",             direction="Input") .....also note, this is new at 10.2.2 (it is not available at 10.2.0) ... View more

Hmmmm, I dont have any more information saying this is a problem thats come back. However, it's a little telling about the problem that deleting the .DAT file "fixes" the issue. If you, Becky, or anyone else still have a .DAT file that causes a crash could you please attach to the forum here?  We can debug and try to figure out whats inside that might be causing the failure. ... View more

Michael, Unsure about your license question. I'd suggest posting to the beta forum. From the above link I posted to beta download, go there, and about half way down on the right is a "FORUMS" button. Someone with more knowledge on licensing should be able to help. ... View more

Jon, If inside the folder the service is deployed to (C:\arcgisserver\directories\arcgissystem\arcgisinput\((service)).GPServer\extracted\v101 You find a .AGS file which is a connection to the Server\ImageService.... yeah its fine. Its talking about copying the connection, not the imageservice contents. If you made a connection to your AGS and placed that file in your working directory, then registered that folder with the server, you shouldn't get a copy on publish message. ... View more

Mark's answer above is correct. Just to expand on it - the tool converts to WGS84 on your behalf if your data isn't already there. Doing this on your behalf it guesses at the best transformation (if one is needed). I'd use the Project tool to be absolutely certain about which transformation is being used and ensure the accuracy of your data as "WGS84" before converting to KML. And of course, Mark's point about comparing to other data is very important. I've seen other "complaints" about data not lining up, and in the end its the imagery that isn't right. The data is "where its supposed to be".  Unless you have/own the data, be skeptical about how authoritative it is, in this case, the imagery. ... View more

Shapefiles, yes. pGDB, no. Pro is 64bit and has the same limitations* that ArcGIS Server and 64bit Background have. *There could be minor exceptions to this rule that I'm unaware of. Layerfiles (.lyr) can be imported into Pro. You cannot save a lyr file. Pro will save lyrx files which are not backwards compatible to 10.x I'd encourage you to give the beta a try. If you still have questions after using it, thats important feedback we'd like to get and address if possible. If you're a named user you can download it from http://pro.arcgis.com/en/pro-app/# (I'm unsure if there are any country restrictions) ... View more

The compressing error is from when trying to make the .SD file. I think theres a few things that could cause it. A couple guesses: --do you have any locks on the data you're consolidating, or are they accessed by something else? (not allowing them to be put into the sd file) --you have write access to the directory you're trying to create the .sd in? --from your screen shot you're executing against 64bit python, but the trace back shows its in 32bit python. Not sure how/why they're crossed. Try running your script from the 32bit Python (note the lack of 'x64' in the path for 32bit). ... View more