Latest Contributions by KimPeter

Hi, You only need to put the port number in the Service field, not port:5151.  I'm guessing that the tool doesn't know what "port" is, so it ignores it and just uses the default service port value.  In your case, the connection works because your service is using the default value.  I bet that if your port was actually 30000, the connection would fail from the Database Connections dialog box. The Geodatabase Connection Properties dialog box must pass the literal value for the service, causing it to fail if the value is incorrect. Try just 5151 in the Service field on the Database Connections dialog box and see if that fixes the problem when choosing versions from the Geodatabase Connection Properties dialog box. Regards, Kim ... View more

I'm sure you probably checked this...but did you make sure the user connecting to the data has been granted the privileges necessary to edit the data?  Are there tables that are related to the datasets you're trying to edit to which the user might also need to be granted privileges? -Kim ... View more

Hi Erik, The SQL Server spatial types are geometry and geography, and they were written by Microsoft.  You'd need to check the Microsoft documentation for information on inserting geometry to a SQL Server spatial type. http://msdn.microsoft.com/en-us/library/bb933876.aspx Hope this helps. -Kim ... View more

Pi-Hellz, The first part of the message indicates that more people are trying to connect to the geodatabase than you have set to allow. There is a setting in the server_config table, CONNECTIONS, that determines how many simultaneous connections you can have to the geodatabase.  By default, this number is 48.  If you need to increase that number, use the sdeconfig administration command utility with the alter operation to set it to a higher number; for example: sdeconfig -o alter -v CONNECTIONS=75 -u sde -D mydatabase -i sde:sqlserver:myinstance (http://help.arcgis.com/en/geodatabase/10.0/admin_cmds/Support_files/admincmdref.htm) The rest of the message makes it sound like your client doesn't have the direct-connect driver it needs.  But if it works sometimes and not others, that doesn't make sense.  If upping the connection property doesn't help, please contact Esri support for assistance. Regards, Kim ... View more

   1. Can I run the post install without re-running the entire SQL Express install? (I've already done this several times and would like to just post-install while I'm trying to fix this)  Yes; you can run just the portion to enable the SQL Server Express instance to store geodatabases without having to reinstall SQL Server Express. The errors you list, though, seem to indicate you're not running the portion of the wizard to enable a SQL Server Express instance to store geodatabases (which only adds the login you specify to the SQL Server Express instance) but rather that you are running the ArcSDE for SQL Server Post Installation wizard, which tries to create an sde database user.     1. CreateSdeUserSqlServer   - SQLState:  NativeError 3916952     2. ArcSDE Post Installation   - Error creating login At what point in the wizard are you receiving these messages?  Can you attach a screen shot? Thanks, Kim ... View more

Hi Liz, I don't think your -g value is valid.  That option is used to specify the type of spatial index and, if applicable, spatial index parameters.  I believe your possible options are GRID,<a grid size> AUTOMATIC NONE RTREE Which ones you can use depends on the DBMS you are using and the geometry storage type used to create the feature class.  (In your example, the -k was not specified, so whatever the GEOMETRY_STORAGE value you have set in your DEFAULTS keyword in the DBTUNE table is what will be used to create the feature class.) However, that error message seems to indicate there's something about the information passed that the DBMS didn't like. Did your DBMS error log file show anything? -Kim ... View more

Hi Joe, You ran the portion of the wizard to enable the SQL Server Express instance to store geodatabases, right?  If so, and you are still getting this message, please contact Esri support so they can help you troubleshoot this. -Kim ... View more

To clarify: You don't need ArcSDE enterprise to create a geodatabase from the database server node in ArcGIS Desktop.  In fact, you can't create an enterprise ArcSDE geodatabase from ArcGIS Desktop at all. To create a geodatabase on a SQL Server Express instance through the database server node in Desktop, you need: -A supported version of SQL Server Express [INDENT]You can run the SQL Server Express installation wizard provided with ArcGIS Desktop or ArcGIS Server Workgroup to install this.[/INDENT] -To run the portion of the installation wizard to enable the SQL Server Express instance to store geodatabases, which writes a key to the Windows registry [INDENT]When you create a geodatabase on a database server, ArcGIS looks for this registry key. If if can't find it, you won't be able to create a geodatabase.[/INDENT] -A connection to the database server from an ArcEditor or ArcInfo level ArcGIS Desktop client [INDENT]If your ArcGIS Desktop license isn't set to ArcEditor or ArcInfo, the New Geodatabase command will be inactive.[/INDENT] -To be logged in to the client computer as an administrator on that particular database server [INDENT]A database server administrator is added at the time SQL Server Express is installed. That initial administrator can add other user logins to the database server administrator role if needed. Only database server administrators have the privileges in the SQL Server Express instance required to create a geodatabase.[/INDENT] ... View more

Hi David, Is the table (parcels) on which you are trying to create your view already registered with ArcSDE and/or the geodatabase?  For example, is "parcels" a feature class you created in ArcGIS, or is it a spatial table you created in SQL Server using SQL? -Kim ... View more

Sukhesh, Are you trying to connect to the second geodatabase using the same ArcSDE service you created when creating the first geodatabase?  If so, that could be your problem. If you use an ArcSDE service to connect, you have to have one for each geodatabase with its own unique name and port. Try making a direct connection to the second geodatabase (syntax = sde:sqlserver:<name of sql server instance>.  If that works, then you probably need to create a second ArcSDE service (if that's how you want to connect to the second geodatabase). Hope this helps, -Kim ... View more

Are you using an ArcView license?  You cannot create new ArcSDE geodatabases with an ArcView license. When I've seen the New Geodatabase option inactive before it was usually due to the Desktop license level. ... View more

Hi, You stated that you installed SQL Server Express, but you didn't mention if you created a geodatabase.  Did you connect to the database server node in ArcCatalog as a database server administrator and create a geodatabase already?  If not, there isn't any geodatabase to connect to so creating a Spatial Database Connection won't work. See this topic for an overview of getting started with ArcSDE geodatabases in SQL Server Express. http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/A_quick_tour_of_setting_up_and_using_database_servers/003n00000099000000/ -Kim ... View more

It is in the Desktop help because it also applies to the ArcSDE geodatabases for SQL Server Express licensed through Desktop.  However, the same information is also in the Server help: .NET http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/index.html#/What_are_database_servers_in_ArcGIS/0093000000wm000000/ Java http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_java_help/index.html#/What_are_database_servers_in_ArcGIS/0092000000vn000000/ On the ArcSDE PDFs....those were done at 9.3 because the ArcSDE topics were all lumped together in the help at 9.3 and people had a hard time weeding out information specific to one database - the PDFs broke them out by database to help remedy that.  At 10, each database has its own section in the help. -Kim ... View more

Hi, Did you happen to switch your Desktop license to ArcView?  Are you getting any particular error message? -Kim ... View more

One last thing - db_owner (a database role) is not the same as dbo.  The similarity in names can be confusing and took me forever to get used to.  If the user is db_owner, it still has to have a corresponding schema with the same name as the user name. ... View more