Latest Contributions by WilliamCraft

This thread is related to your previous thread at: http://forums.arcgis.com/threads/87289-Error-SdeParseHandlers-fatalError()?p=310715#post310715.  Please see my response to that initial thread: "The error you provided seems like one that is related to the metadata associated with one or more of the feature classes you are trying to copy. You could try a couple of things to identify whether it is one feature class or multiple. One thing to try initially would be to preview the metadata for each of the feature classes within the feature dataset you are trying to copy using the Metadata tab in ArcCatalog. For the one(s) that might throw an error when doing this, my suggestion would be to create an feature class within the SDE instance you are wanting to copy to and then to load the data separately using the Simple Data Loader or the Load Objects tool. Doing this might exclude the metadata altogether and remove it as part of the overall equation when copying the data. If that works, then try importing the metadata into the newly-created feature class (there are a few ways to do this, especially at 10.0 and above). If importing the metadata revives the errors, you probably have issues with your metadata or with the metadata template that need to be addressed." ... View more

Are you attempting to build the network as the schema owner or as SDE?  Otherwise, does the DBMS user account you are using have permissions to the tables (base, F, S, A, D) of the objects participating in the network? ... View more

I found a related table that was selected to participate in the replica and it was related by way of a Simple M-N (many to many) relationship class.  At the FGDB level (i.e., the replicate) I am not sure how this is handled because of the fact that an RDBMS will create an intermediary table to act as a sort of "pivot table" in this situation.  In other words, I am not certain whether or not simple, one-way replication even supports a M-N relationship at 9.3.1 SP2.  So, I've unregistered the replica and re-created it without the related table to see if that allows changes to be applied.  More to come once some time passes... ... View more

Good point, Marco, about the lock topic.  I've pulled the SQL for the LOCK_UTIL package and listed it below.  When it gets to the object locks section, I can see that it is supposed to add an object lock and subsequently delete one thereafter.  It's possible that I may need to seek some help eventually in inserting some debug code as you suggested.  I went ahead and wrote a script to iterate through all of my feature classes to determine whether there were in NORMAL or LOAD_ONLY mode.  All of them came back as NORMAL.  I will continue to troubleshoot and reply if I identify a fix/solution.  Unfortunately, I am not having much success with Esri tech support on this issue at the moment.  We have a few more steps to try.  Thank you again, Marco.  Your input is much appreciated.  SQL Code from package is below... ***************************************************** CREATE OR REPLACE PACKAGE SDE.lock_util IS   /* Type definitions. */    SUBTYPE layer_lock_t IS SDE.layer_locks%ROWTYPE;    SUBTYPE layer_id_t IS SDE.layer_locks.layer_id%TYPE;       SUBTYPE state_lock_t IS SDE.state_locks%ROWTYPE;    SUBTYPE state_id_t IS SDE.state_locks.state_id%TYPE;       SUBTYPE table_lock_t IS SDE.table_locks%ROWTYPE;    SUBTYPE table_id_t IS SDE.table_locks.registration_id%TYPE;       SUBTYPE object_lock_t IS SDE.object_locks%ROWTYPE;   /* Constants. */    -- The following constant defines the release of lock_util and is used by    -- the instance startup code to determine if the most up to date version of    -- the package has been installed.    C_package_release       CONSTANT PLS_INTEGER := 1008;    -- Constant names for autolock parameters.    C_is_autolock           CONSTANT CHAR(1)  := 'Y';    C_is_not_autolock       CONSTANT CHAR(1)  := 'N';       -- Constant names for lock types.    C_shared_lock           CONSTANT CHAR(1)  := 'S';    C_exclusive_lock        CONSTANT CHAR(1)  := 'E';    C_marked_lock           CONSTANT CHAR(1)  := 'M';    C_shared_lock_all       CONSTANT CHAR(1)  := '-';    C_exclusive_lock_all    CONSTANT CHAR(1)  := 'X';   /* Procedures and Functions. */    -- The following functions perform operations for layer locks stored in    -- the SDE.LAYER_LOCKS table.  Each operation is an autonomous transaction.    PROCEDURE add_layer_lock (layer_lock  IN  layer_lock_t);    PROCEDURE delete_layer_lock (sde_id    IN  pinfo_util.sde_id_t,                                 layer_id  IN  layer_id_t,                                 autolock  IN  VARCHAR2);    PROCEDURE delete_layer_locks_by_sde_id (sde_id  IN  pinfo_util.sde_id_t);    PROCEDURE update_layer_lock (layer_lock  IN  layer_lock_t);    -- The following functions perform operations for state locks stored in    -- the SDE.STATE_LOCKS table.  Each operation is an autonomous transaction.    PROCEDURE add_state_lock (state_lock  IN  state_lock_t);    PROCEDURE delete_state_lock (sde_id    IN  pinfo_util.sde_id_t,                                 state_id  IN  state_id_t,                                 autolock  IN  VARCHAR2);    PROCEDURE delete_state_locks_by_sde_id (sde_id  IN  pinfo_util.sde_id_t);    -- The following functions perform operations for table locks stored in    -- the SDE.TABLE_LOCKS table.  Each operation is an autonomous transaction.    PROCEDURE add_table_lock (table_lock  IN  table_lock_t);    PROCEDURE delete_table_lock (sde_id    IN  pinfo_util.sde_id_t,                                 table_id  IN  table_id_t);    PROCEDURE delete_table_locks_by_sde_id (sde_id  IN  pinfo_util.sde_id_t);    -- The following functions perform operations for object locks stored in    -- the SDE.OBJECT_LOCKS object.  Each operation is an autonomous transaction.    PROCEDURE add_object_lock (object_lock  IN  object_lock_t);    PROCEDURE delete_object_lock (object_lock  IN  object_lock_t);    PROCEDURE delete_object_locks_by_sde_id (sde_id  IN  pinfo_util.sde_id_t);    -- The following procedures delete layer, table, state, object locks    -- stored in SDE.LAYER_LOCKS, SDE.TABLE_LOCKS, SDE.STATE_LOCKS,    -- SDE.OBJECT_LOCKS respectively within a single autonomous transaction.    PROCEDURE delete_all_locks_by_sde_id (sde_id  IN  pinfo_util.sde_id_t);    PROCEDURE delete_all_locks_by_pid (pid  IN  pinfo_util.sde_id_t);    PROCEDURE delete_all_orphaned_locks; END lock_util; ... View more

Thank you, Marco.  This is helpful in troubleshooting further.  I had also performed an Oracle trace at the same time as the SDE intercept.  When reviewing the trace file via OraSRP, I was able to better identify what I was seeing with the lock identifier syntax that you commented on earlier.  In general, below is how I believe the identifier works: Lock <sde_id,version_id,object_type,application_id,autolock> as translated from Lock <220772,22580,1,999,N> The types of values described above were used in the following SQL as shown by my trace file: DECLARE object_lock SDE.lock_util.object_lock_t; BEGIN /* ArcSDE plsql */   object_lock.sde_id := :sde_id; object_lock.object_id := :object_id;   object_lock.object_type := :object_type; object_lock.application_id :=   :application_id; object_lock.autolock := :autolock; object_lock.lock_type :=   :lock_type; SDE.lock_util.add_object_lock (object_lock);:sql_code :=   SDE.sde_util.SE_SUCCESS; EXCEPTION WHEN OTHERS THEN :sql_code := SQLCODE;   :error_string := SQLERRM; END; I agree in that it seems as though an attempt is made to delete an object lock but the lock is not there.  What is really interesting to me is that the trace file contains a few sde_id values throughout but never the '220772' as found in the SDE intercept files. ... View more

If you perform the unregister on the replica as the replica owner (user) it works cleanly.  If you do this as any other user (even as SDE) it may not get deleted entirely, requiring the use of SDE command line to delete sync send versions.  That's been my experience at least... ... View more

Within the same folder as your geodatabase, add an already-existing file such as a text or MS Word file; then try to edit it and save changes.  Do you get similar results when attempting to save edits to that file?  It may be that your entire volume is read-only despite what the security settings indicate within Windows. ... View more

If you are looking to autopopulate a field based on the value of OBJECTID, your best bet is to create a Trigger in my opinion.  When a new record is added and the OBJECTID value is autogenerated by ArcSDE, your trigger will be able to use that value to determine the value of your custom field.  However, the trigger will need to fire after the OBJECTID trigger from ArcSDE fires.  There is some great online help available for creating basic triggers like this for both Oracle and SQL Server depending on which RDBMS you are using.  If you are not using an RDBMS, your options are much more limited and you'll need to take a different approach... most likely using a Python script which is run on a periodic basis. ... View more

When I look at this error and thinking back about my experience with Geoportal 1.1.1, to me it sounds like something is configured wrong within the GPT.XML file in the Synchronizer Parameters section.  Another possibility is that your Geoportal host machine has ports blocked due to firewall issues.  I would try taking down the Windows Firewall (and any others like McAfee or Norton) first, and then if that doesn't resolve the issue I would review the Synchronizer Parameters in the GPT.XML file.  Is it possible that your ArcGIS Server services are secured?  Start there and let us know what you find out. ... View more

Switching the configuration over the Simple Authentication instead of LDAP Authentication results in the exact same behavior, which is that the application seems to always say "Welcome" despite whether I click Login without entering any credentials or whether I actually input a valid set of credentials.  At this point, I have reviewed the Fiddler traffic associated with these steps and I am not seeing any communication between the server which contains Geoportal and Tomcat with the server containing MS Active Directory.  I have followed the Apache Tomcat 6 installation instructions and also made the necessary configurations for Tomcat to work well with IIS (http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html).  Any suggestions for further methods of troubleshooting would be greatly appreciated. ... View more