Latest Contributions by deleted-user-vpHnfyiCToFz

Ezequias, I've converted the python scripts to auto synch on a schedule from the database server.  That way, I don't have to worry about which version of the native client I have on the machine running the synchronization.  Call me 'Garfield' or Lazy IT.  I just don't want to experience these errors anymore.  I've been running this from the Database server for over a year without complications.  Try testing the synchronization from multiple native clients to see if you get the same response. Luke ... View more

Has this been or is going to be resolved?  Anyone have a fix for honoring field order in the map service? ... View more

There are no plans to change this default setting, as this is by design. The default design of the locator is to not return match results when you build the locator without zones and do not include zones with the input address because of the performance cost when having to search through the entire index of the reference data to return multiple candidates, which would take longer to do. Of the multiple candidates returned, there may be many that are correct. You wouldn't know which is the correct candidate to be matched if you didn't have a zone.  The performance hit would be really significant for larger geographies, but I know a lot of customers create local locators for their city or county and create them without referencing a zone cause it's all the same.  But, just about every city has a Main St�?� how do you know which Main St is correct if the county has multiple cities and they all have a Main St? Or like in Chicago, IL, the street Lake Shore Drive spans 15 different zip codes. The article "Dual Ranges address locators created with ArcGIS for Desktop 10.1 do not return matches" provides a more permanent solution that modifies the USAddress locator template to make 'Yes' the default setting so you don�??t have the change the properties of every locator after you create it. The match with no zone setting was also discussed in the Geocoding -Advanced Techniques technical workshop at the 2012 International User Conference, which can be viewed in the demo  between time frame 20:49 -  20:06. The corresponding slides for the time frame in the demo can be found at http://proceedings.esri.com/library/userconf/proc12/tech-workshops/tw_2022.pdf starting at Managing Performance. I hope the above information helps and if it does not, please submit a request to Technical Support. -Shana Thank you for sending the geocoding behavior change in 10.1 information to the forum discussion. ... View more

I'm using the 2008 R2 client and still getting this message when trying to synchronize. All of this is so fragile, I'm a little worried to even think about using it with a client. I've setup an autosynch replica python script to run under windows task scheduler on another system.  It has been running for three months now without any complications on the work around.  If you are still having problems, I would think there is something else going wrong with your connections. It is definitely a weird bug.  I would have expected a patch by now. ... View more

What's the ETA on the fix for this bug?  I really don't like mixed matched versions of software in an enterprise network.  Call be 'OCD' but seems a bit odd to me. Workaround worked; at least it still is working for now. ... View more

The nim NIM086855 is close to the earlier discussion/report on this synchronization issue. The workaround is listed as "Using SQL Server Native Client 2008 R2 for the ArcGIS Desktop machine to synchronize changes." Please contact Technical Support to confirm if this is the exact case encountered and/or regarding the workaround. Thank you, Mandar We had an issue connecting to sql server 2012 databases using the sql native client other than using the sql native client 2012...identical release version as the database.  If you use the one that comes with the sql server 2012 install media kit, it doesn't work.  Going to Microsoft website downloading the latest fixed the connection issues with ArcGIS Desktop.  Can you validate that the NIM086855 is set to be released in the next service pack? ... View more

just got off phone with with ESRI and no luck so far. For what its worth, when I run the synch tool from toolbox instead of the wizard tool bar i get the 'table already exists' in the results messages but also get a 'error 000582'.........which unfortunately is a catch-all type of error. Mandar, is there a bug reported? Because if not right now i'm not seeing any resolution or work around and if I understand what you're saying correctly if you have conflicts and if you have a 2012 DB server...you're outta luck? I'd suspect that there are a lot of people with this deployment scenario. I have seven deployments in which two are using replication.  If this is a 2012 DB server issue, this needs to be fixed ASAP.  All my new deployments are built on sql server 2012.  It doesn't make sense to deploy on older versions. ... View more

It seems that this issue is reproducible only with Sql Server 2012 and originates only when conflicts are present during the synchronization. Any successive synchronizations, even with new replica registered on this geodatabase, seem to encounter the "Table already Exists" error. The issue does not seem reproducible with other versions of Sql Server (for e.g. Sql Server 2008 R2.) - Mandar Is this fixed in upcoming patches or service pack 2? ... View more

I got this error as well.  What a worthless message!  I'm planning on just recreating the replica.  Currently on ArcGIS 10.1 sp1.  Didn't see this message until after service pack was applied. ... View more

As a followup, I have two question for ESRI or someone who has tested this scenario.  1.  Will ArcGIS Server 10.1 sp1 support windows server 2012? 2.  Is there an advantage to move my ArcGIS Server 10.1 Virtual Server from windows server 2008 r2 to windows server 2012 or will it perform the same if I keep my VS at Server 2008 r2 under a hyper-v 3.0 environment? ... View more

I do not see bug #NIM081790 being addressed in ArcGIS 10.1 SP1.  Can someone from ESRI confirm that this will indeed be fixed in sp1? ... View more