Latest Contributions by RobertNalewajk

Hi,  thanks for your persistence in this! To answer your questions in reverse order I'm using a SQL Server Enterprise Geodatabase.  ArcGIS 10.4, SQL 2012 SP3.  for the initial testing I was using an Enterprise database that I had previously created for some data work, but wanted to create a new one "from scratch" just for this testing, sorry for the confusion. for the failure - after publishing (no errors during analyze) - I get: "Packaging succeeded, but publishing failed.  ERROR 001487: Failed to update the published server with the server-side data location.  Please see the server's log for more details.  Please conuslt the GP Results Window for enhanced error description or contact your administrator for the server logs." The GP Results Window shows a successful Stage Service, but a failure to upload the service definition (I have published other services while this issue has persisted so it shouldn't be a standard publishing issue).  The GP window shows errors 001487 (as above) and Error 001369: "Failed to create the service." The Server logs show me 3 errors (all severe). 1. Failed swizzling service 2. Failed to create the service: Updating the server connection string for layer TimeTestPoint Archive failed.  Attempted connection string was: . . . Table name is TIMETEST.DBO.TIMETESTPOINT_H.  Please verify the data exists on the server. 3. Error executing tool.  PubishServiceDefinition . . . Errors 001487 and 001369 as above. the 2nd error seems to be the diagnostic one here to me, although I don't understand why its happening.  The connection string that is registered with Server is the same connection string the data is added with so access shouldn't be an issue. thanks again! ... View more

Thanks Berend, that's all working great for me except for the last point - my publishing keeps failing and I can't figure out why.  maybe I'll try putting together a new from scratch geodatabase and give it another go.  I'll let you guys know if there is any progress. thanks! ... View more

ahh - I think the confusion might be that the data I'm talking about is versioned - which, based on the link you added, works differently than non-versioned data when archiving.  I didn't know they were treated differently. to clarify I'm working with versioned data.  thanks! ... View more

Michael Robb, thanks for your replies, I'm having trouble replicating some of the items you mentioned and am wondering what I'm misunderstanding.   If it makes a difference I'm talking about a SQL Server 2012 Geodatabase at ArcGIS 10.4.0 for my current DB environment, with ArcGIS Server 10.4.0 unfederated.  I'm not sure it does, but you never know. When I enable Archiving it looks to be creating a "FeatureClass"_H table.  So if the feature class is GIPractice the historical (or archive table) is GIPractice_H (checking the source of the "Historical Archive" layer added with the Geodatabase History Toolbar backs this up).  The time control fields in there seem to be GDB_FROM_DATE and GDB_TO_DATE, although the created_date and last_edited_date also appear. When I look at the GIPractice_evw view query in SQL Server manager I don't see any reference to the GPIPractice_H table, and can't seem to find records that are deleted, but are visible in the "_H" table.  Also, when I pull the feature class into ArcMap and make it time aware the GDB_FROM_DATE and GDB_TO_DATE fields are missing, only the created_date and last_edited_date fields are available, and they only seem to show the current data. what am I missing here? I felt like I was finally getting a hold on some of this background DB stuff and it seems like I'm missing something important here. thanks in advance! ... View more

I'm experiencing the exact same issue.  I would like to publish the archive table as a layer to allow a user to see what the data looked like at specific times in history, including data that has been deleted in the current version.  I also tried to create a view with the archive table and publish that, but was also unsuccessful. any tips would be helpful! thank you! ... View more