Skip navigation
All Places > Esri Technical Support > Blog > 2010 > June

ArcGIS 10 Availability

Posted by geonetadmin Jun 30, 2010
Esri logo

06/30/10 - We had an overwhelming demand for downloads of ArcGIS 10 today. This exceeded our initial estimate for the number of visits to the Esri Customer Care website ( ). Due to the increased traffic, our systems could not meet the expectations of our customers this morning. We acted swiftly to resolve the issue and have since increased the available capacity of the Web site to meet the demand. We apologize for any inconvenience this may have caused you, and we invite you to try downloading again.  If you run into any issues, please contact Esri at 1-888-377-4575.

Mike H., Program Manager
User Advocacy Group, Esri Support Services

Mike H., Program Manager
 Follow me on Twitter:
ArcGIS 10 product

We at Esri have been hard at work for many months to prepare for the ArcGIS 10 release. Today, the day is finally here when we can announce that ArcGIS 10 has been officially released.

For the first time, ArcGIS will be available as a download, which reduces the packaging waste and any delay due to production and shipping. It’s part of Esri’s effort to be a Greener company, and we hope that many of you will participate in this effort by downloading the software. For those that still require a physical disk, there is a way to request to receive backup media on DVD, but it will take a few more weeks (details for this are in the e-mail you will receive from Customer Service).

In the United States, maintenance contacts will receive information by e-mail on how they can download and authorize ArcGIS 10 for their organization. They may also contact Esri Customer Service for questions about their order at 1-888-377-4575 option 5; outside the United States, customers should contact their local Esri Distributor.

Esri Technical Support has been supporting the ArcGIS 10 Beta/Pre-Release for the last 8 months and is ready to take your calls or technical questions related to the 10 Release. If you run into an issue with the download, installation or use of the product, we are here to help.  Please contact us at 1-888-377-4575 option 2 or submit a request via the online form. Outside the United States, customers should contact their local Esri Distributor.

For more information on ArcGIS 10, see

Press Release:  ArcGIS 10 Transforms the Way People Use GIS.

Mike H., Program Manager
User Advocacy Group, Esri Support Services

Mike H., Program Manager
 Follow me on Twitter:

Farewell to VBA

Posted by geonetadmin Jun 25, 2010
A Farwell to VBA
Used to use it everyday
But now VBA is going away
This blog is here just to say
Farewell my friend, VBA

Some of you may already be aware that VBA will be deprecated after version 10 of ArcGIS Desktop.

Microsoft discontinued distributing VBA licenses to new customers as of July 2007 and encourages customers to use .Net Framework, instead. Esri has decided to be coherent with Microsoft’s stance on VBA. The word has been out there since this Developer blog post was published last year: VBA and VB6 with ArcGIS: What’s the Story?

Please refer the following blog post for additional details about VBA support in ArcGIS Desktop at 10: ArcGIS Desktop and VBA?

For further information on support for VBA, please see page 5 of the Product Deprecation Notice.

Please provide any questions or comments that you may have via the comments section below this post. NOTE: You must be logged in to your Esri Global Account to leave comments.

- Kaushik M., Support Analyst, SDK group - Esri Support Services

Help button

With any programming language or script, there are always going to be times when things just don’t work. When that happens, what exactly can be done to fix it?

To fix the script, you first have to determine the exact problem, since it’s not always evident. Below are three issues or problem areas to check when your Python script is not functioning.

Problem 1: Error in the code

One of the most common problems when using a programming language is that there is an error somewhere in the code. The easiest way to check for an error is to find the error message (if any) that’s being returned. Most error messages are about a specific line in the code that is not working.

Finding out what the error message is can be very easy to do, especially when you’re running the script in an Integrated Development Environment (IDE) like PythonWin or Python IDLE. Unless you have programmed try and except statements* into the script, the script will output the error and the number of the line on which it occurred. This makes it very easy to track down.

Below is an example of what a typical error response looks like in PythonWin:
screen shot of typical Python error message

The first thing to look at is the line number. Note that it reports back two lines, but the one to look for is the one directly after the name of the script being used ( in this case) – See Arrow 1. The line directly below that is the actual line from the code itself - See Arrow 2.

If the problem is with a tool or method, it may give you an ArcGIS error code that has information about the error – See Arrow 3. In the sample’s case, the file path did not exist, so the fix would be to check the path. If you are unsure about the tool errors, then you can search for the error message in ArcGIS Desktop Help by typing in the numeric code (for example, 000732). Help documents include possible solutions to each error.

Note: Be sure to double and triple check file paths or any long strings, as one typo will cause errors. When possible, copy/paste long strings to minimize typos.

Note: If the error reports a problem on Line 1, then it might not be the code but another dependency (for example, the module being imported does not exist).

*Why do try and except cause issues when reviewing error messages? Try and except are used for error checking and validation procedures, and if included without a way to output the error message, it can disguise the error, therefore making it very hard to find. For more information on Try/Except statements in error handling, see the ArcGIS Desktop 9.3 Help topic entitled, Error handling in Python.

Problem 2: Incorrect Python Version(s)

Python is a flexible language and allows multiple versions to be installed on one machine. This can cause problems when programs like ArcGIS require the use of a certain version, and the machine is trying to use a different one. Each version of ArcGIS requires a specific version of Python to be present on the machine and will install that version when ArcGIS Desktop, ArcGIS Engine, or ArcGIS Server is installed. Below is a table of ArcGIS versions and the respective Python version:

ArcGIS VersionPython Version

Okay, so now that we know what version we are supposed to have, how do we go about checking which version is being used? Every file type in Windows uses a default program to run that file type. In Python’s case, it is python.exe, which is typically located in the system folder where Python was installed. By default, ArcGIS installs its version in the C:PythonXX directory, and the python.exe is located in that directory.

To check which version of Python is being used, open Windows Explorer and go to Tools > Folder Options > File Types tab, or if you are using Windows Vista or 7, go to Control Panel > Default Programs > Associate a file type and find the PY extension listed there. Selecting it will tell you what program is being used to run that particular file type, and on Windows XP, clicking the “Advanced” button will allow you to see the path to that file under the “open” action.

File Type dialog boxes in Windows XP
File Type dialog boxes on Windows XP

In addition to the Python version being incorrect, there is also the possibility that the IDE version being used is incorrect. This is especially true with PythonWin. To verify which version of PythonWin is being used and to make sure it matches the correct ArcGIS version, start PythonWin with the Interactive Window open and it will display the version.

Interactive Window

Problem 3: Missing dependencies or modules

When working in any programming language there are times when using outside libraries or modules is necessary. If you are using these libraries, the script needs to be able to find them in the defined location.

Python, by default, installs all the modules (PY files) in the Lib folder of the Python installation directory. If you are using a custom module, be sure to verify that it is installed in the correct location on the machine, as it can vary. For example, the arcgisscripting module is installed in the bin directory of the ArcGIS installation folder, not in the Python installation directory.

Remember that modules are just other PY, PYC, or PYD files on the machine and are added by the import statement in code.

In closing, remember that the ArcGIS user community and Esri Support Services, both in the U.S. and our international distributors, are here to help. Be sure to check out the Geoprocessing forum and the Script Gallery for tips and ideas. Happy Pythoning!

- James U., Support Analyst - SDK group, Esri Support Services

esri logo

For updated information and a link to download a patch for this issue, please see the UPDATE: Patch available for ArcGIS 10 Geodatabase issue with synchronizing replicas blog post.

Customers who plan to use ArcGIS 10 with geodatabase replication need to be aware of an issue that causes synchronization to fail. Full details are available in Knowledge base article 37896.

Esri is working on a fix that should be available soon. For updates on status, you can use bug number NIM058231 — Upgrading geodatabases with replicas to version 10 causes synchronization process to fail. 

We will keep you posted via this blog as updates become available.

Mike H., Program Manager
User Advocacy Group, Esri Support Services

Mike H., Program Manager
 Follow me on Twitter:

How did you get so good?

Posted by geonetadmin Jun 18, 2010
boys on tricycle

It happens all the time – I’ll be on the phone with a user who needs some help with an unfamiliar function or extension and they’ll ask the question, ‘how did you get so good at this?’

As much as I would love to credit my fancy college degree or my natural inclination to know-it-all, I have to be honest – I learned on ArcView 3.3 in university (which doesn’t help me much now), and I definitely do not have a psychic ability to glean answers from the great beyond.

So, if I did not ‘get so good at this’ from my university studies, and I don’t spend weekends working for a psychic chat line, then where did I learn all of this? The answer is simple. I learned just like you are now: reading blogs and forums, studying the Help documents, asking questions of others, taking Esri Instructor-Led and Virtual Campus classes, and trying things over and over again until I found the correct answer.

If your company has a training budget, then signing up for an Esri Instructor-Led or Virtual Campus course is a great way to learn about GIS. Instructor-Led courses no longer require you to travel to an Esri training site; Virtual Campus classes have been created so you can learn from an instructor via the Internet or video conference. In addition, the Virtual Campus classes are a less expensive and self-paced option to get training on a variety of products and technologies. More information on these training options can be found by going to the training site.

Now some of you may be saying, “The company I work for doesn’t have a training budget right now. How can I learn without training!?”

The answer is simple. With the purchase of ArcGIS Desktop 9.x or 10, you receive free, and I mean totally free, and useful training materials. Since free is my favorite price (and probably the favorite price of the company you work for), this would be a great option for learning more about GIS.

First things first, you need to install ArcTutor using the Complete option. ArcTutor comes with your ArcGIS Desktop Installation disk. If you aren’t sure if ArcTutor was installed, you can check by going to Add/Remove programs and looking for the following:

add/remove programs

If it is not installed and you are not the keeper of the disks, please contact your IT department and request they install the ArcTutor disk using the Complete option.

Once you are sure ArcTutor is installed, you will have access to dozens of tutorials that will help you learn the software.

If you are using a 9.x version, simply navigate to the following location in Windows Explorer: C:Program FilesArcGISDocumentation.

list of documentation files

Here you will find an assortment of tutorials that walk you through exercises using the ArcTutor data.

If you are using 10, accessing tutorials is as simple as looking in Help. I would recommend using the Web-based 10 Help, because it is updated frequently versus the Help dialog box installed on your own system, which is only updated when you install a service pack. Keep in mind that ArcGIS 10 is a major release; new documentation and tutorials are in the process of being written, and any new tutorials will be available via Web Help before being available on your locally installed version. To link to the tutorials on Web Help, click here.

If you need to use your locally installed Help dialog box, open Help and go to Essentials Library > Getting started with ArcGIS > ArcGIS Tutorials.

Use these tutorials to get familiar with processes, functions, or extensions for free. Soon YOU will be answering the question ‘how did you get so good at this?’.

Please provide any questions or comments that you may have via the comments section below this post. NOTE: You must be logged in to your Esri Global Account to leave comments.

-Allison R., Technical Account Lead, Esri Support Services


Ever wonder why you get asked what your configuration is every time you call into Esri Support Services (ESS)? There is a method to our madness! Following up on a previous blog (Coming to a Resolution Near You), ESS does care what service pack you are using as well your operating system, database versions, and even if you are operating within a virtualized environment. We are inputting this information into our product drop-downs within each incident, which is then stored in our call tracking system. While we do have a record of what you last called in about, it is often the case that you may be a different contact, have recently upgraded/applied a service pack/patch, or may even be working on a different system than was previously being used when we last worked with you. Getting this out of the way initially might save you some serious time in troubleshooting your issue, as versions, service packs, and even bit versions can determine if you are encountering a known issue or bug.

It is also still important for us to get your configuration regardless of the type of issue you are seeking assistance on, as the configuration may come into play down the road. If you are just calling in about a general question, the functionality or behavior of what you are seeking help on may change between versions, so this is still important to document and have a clear understanding of.

The Product drop-down section is kept within each incident:

Feel free to let us know if you still have the same configuration as the last time you called in. Also, another helpful step when logging Web/email incidents is to copy/paste this information into a document and keep it handy to include in your requests. To take this even further, you can use the new webform and save your profile information under system configurations within your requests. More on this functionality within the webform can be found here in a previous blog post.

Keep your questions and issues coming and your configuration handy!

- Melissa J., Geodata Group Lead, Esri Support Services

esri logo

With ArcGIS 9.3.1 SP2 scheduled to be available in July 2010, there is a targeted list of issues that are planned to be addressed in SP2. This list is subject to change at any time, and Esri will continue to add additional items. The following link is to the PDF file that contains the detailed list of the issues that are planned to be addressed in ArcGIS 9.3.1 SP2: ArcGIS 9.3.1 Service Pack 2 Announcement.

Mike H., Program Manager
User Advocacy Group, ESRI Support Services

Mike H., Program Manager
 Follow me on Twitter:

Hello, this is Cassandra with a cool solution for cleaning inaccurate point data. I worked with a customer recently who had received a data set with points representing residential electrical meters, which unfortunately had a lot of duplicate points. The customer was able to remove the identical duplicates by using the 'Delete Duplicated Features' script available from ArcScripts, but he found numerous other points that were obviously duplicates but were not identical geographically. Most of these erroneous points were within 2 centimeters (cm).

As the dataset contained thousands of points, manually searching the entire data set was out of the question, so the customer turned to Esri Support for ideas on identifying the duplicate but not identical points so he could delete them.

With the help of a colleague, we provided the following solution: create a buffer on the points dataset with an extremely small radius value, for example 3 cm.

Run an intersect on the buffer polygon result. Because the buffers are tiny, the only polygons in the intersected results will be located where two points are within 6 cm of each other.

The customer was then able to zoom to each of these polygons from the attribute table and manually delete the erroneous point.

This method may not work for every situation, but is a good example of how to use some of ArcMap tools to tackle a problem.

Please provide any questions or comments that you may have via the comments section below this post. NOTE: You must be logged in to your Esri Global Account to leave comments.

- Cassandra L., Desktop Support Analyst, Esri Support Services

This is John again with the Implementation team. Today, I want to look at another aspect of the ArcGIS 10 release: upgrading your server.

I'd like to start by reiterating Mostafa's point from his earlier blog post - the best preparation for a major software upgrade is "testing, testing, and more testing". This is especially true for server products, as quality of life for System, GIS, and DB Administrators is often determined by uptime. As a rule of thumb, try not to make any changes to the production environment that haven't already been tested on a low-impact system. At the very least, perform upgrades at a time when you'll be able to troubleshoot and fix any issues without impacting your organization.

Second, I'd like to mention some files and folders that are important to ArcGIS Server. It's great to have a full system backup, but it can also be helpful to back up these specific items so they can be restored without rolling the entire system back. ArcGIS Server stores configuration files, map services, and security settings in C:Program FilesArcGISserver. When backing up, feel free to ignore the serveruserlog folder - it can become huge depending on how you have logging configured. These same folders can come in handy when reinstalling or migrating to a new system.

It's a good idea to have a backup of your web content. There are too many variables to list everything in a blog post, but here are a few resources on migrating web applications that should outline what you'll need:

One last note - the best, most complete information on migrating can be found on our Web site. Here are a few resources to look at before upgrading:

-John P, Senior Implementation Support Analyst, Esri Support Services

As Esri prepares for the final release of ArcGIS 10, the downloads for Pre-Release will no longer be available on the customer care portal after June 4th, 2010.

We thank you for all of your participation and feedback during the Beta/Pre-Release cycles of ArcGIS 10.

Mike H., Program Manager
User Advocacy Group, ESRI Support Services

Mike H., Program Manager
 Follow me on Twitter:

Filter Blog

By date: By tag: