Latest Contributions by JakeSkinner

Execute the Setup.exe for ArcSDE and only check the option 'Enable geodatabase storage on SQL Server Express'.  After you complete the wizard, detach and then reattach the database using ArcCatalog.  If you still cannot make more than 3 connections, try creating a new geodatabase and test to see if you can make more than 3 connections. ... View more

Try importing your shapefile into a File Geodatabase and see if you experience the same behavior. ... View more

Unfortunately I had to remove the "answered".  While you can remove the database reference to the user and remove him from the list of "Sdemon -o info -I users".  Deleting the line from the database does NOT remove the GSRVR.EXE that the user is using.  Eventually you get enough of them and SDE refuses any more connections -- Even if it says you only have 12 users on the instance. Sorry Jake, but your solution doesn't work.  Brent Brent, It looks like you are connecting to you SDE geodatabase using an ArcSDE service.  Have you considered using a direct connection?  This is usually the recommended way to connect an SDE geodatabase.  Advantage: The direct-connect architecture moves ArcSDE functionality to the  desktop. This removes the ArcSDE load from the server and allows  additional resources to be freed up for the DBMS, which means you get  better scalability on the database server.Direct  connections can be faster if the server is heavily used, because  processing takes place on the client machine. Rather than having to  process the information on the server, which may be responding to  requests from numerous other users at the same time, and send the  information back to the client across the network, the client computer  is typically only processing a few tasks at a time.   Direct Connections will also not spawn any GSRVRs.  If you must use an ArcSDE service to connect to the geodatabase you should set the TCPKEEPALIVE parameter to TRUE.  Doing so will clean up any orphaned GSRVR processes.  Please see the following KB article. ... View more

This is definitely strange behavior.  I've tried the solution from the following thread here, and I also tried editing the registry as stated in the help to load all add-ins regardless of whether or not they have digital signatures.  Neither have worked.  I'm installing Service Pack 1 for Visual Studio 2010 to see if this will make a difference. ... View more

Hi Heather, This will be part of the core functionality at 10.1 with Editor Tracking.  This functionality records who edited which features.  You can see an example within the following video: http://video.arcgis.com/watch/428/to...r-desktop-10.1 ... View more

Hi Peter, The Auto-Complete tool is designed to only work with features in the same feature class.  As a workaround you can use the Trace tool.  Digitize your new feature (i.e. Crop Field) from one area along the Farm Dam boundary to the other.  After clicking on the Farm Dam for the second time (as if you were ready to auto-complete), click on the Trace tool.  Click on the last location and begin tracing the boundary of the Farm Dam to the first location. ... View more

I would recommend using the new mosaic dataset that's available for ArcGIS 10.  Creating the mosaic dataset will be much faster, you will receive much better performance, and you do not need to use a python script to create one. ... View more

Right-click on your SQL Server instance in the Catalog window > Permissions.  Do you have any Windows Groups listed here?  If you do, temporarily remove the windows group.  Afterwards, try creating the geodatabase.  If this works add the Windows Group back to the instance. ... View more

As a test, can you copy the problematic feature dataset to a new File Geodatabase.  Then add the feature classes to a new Map Document.  Does the same problem occur? ... View more

What are the field types for the shapefile and for the SQL Server table that the join is based off of? ... View more

You can find out which Windows Group has the default schema using SQL Server Management Studio.  Navigate to the database > Security > Users.  Right-click on the Windows Group > Properties.  Here it will state what the default schema is.  You can remove the default schema from the Windows Group by deleting the schema from the geodatabase by going to the database > Security > Schemas > right-click on the schema > Delete. The users that are a part of this Windows Group should still be able to connect to the geodatabase successfully. ... View more

Does your feature class contain a field of type 'Long Integer' or 'Short Integer'?  This is required when creating a subtype. http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//005r00000003000000.htm ... View more

Hi Max, It looks like you added a windows/domain group to you SQL Server Instance and then set a default schema for this group.  This is not allowed: http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/7d46a024-7ed5-4c9b-b091-3640dc04f5a1 Try removing the default schema from the windows group and then try creating the database. ... View more

I tested with ArcSDE 10, but I it should be the same for 9.2.  I was able to compress my database to a state of 0 without unregistering any of my replicas.  Here are the steps I took: 1.  Reconciled and posted each child version to the SDE.Defeault version 2.  Deleted the child versions 3.  Synchronized each replica 4.  Disconnected all users from the geodatabse 5.  Ran a compress Can you try the same steps and see if you can reproduce? ... View more