i am using DRM 22.214.171.1246 and am trying to export a newly created repo. i've created it by using the option for "Dell Openmanage Essentials inventory". but when i try to export it so i can use it locally it hangs at 95% and does not continues. Details messages also states :
279. 2/1/2017 3:52:35 PM Export Repository : Successfully downloaded update 139/140 : 647762a98faa8090d23023bca3643a7b.EXE
280. 2/1/2017 3:52:42 PM Export Repository : Starting to download update 140/140 : Diagnostics_Application_54KCN_LN_4239A33_4239.41.BIN
281. 2/1/2017 3:52:45 PM Export Repository : Exporting catalog...
anybody any ideas where to look for this?
i am running Windows 2012 R2 on the OME and repo server.
Can you please check the output location and see if catalog.xml is created?.
Please check the log file
and see any error message available?
i had a look at the logs you suggested but they are from yesterday.
01-02-2017 15:38:22 Exception writing job file entry to DBAn error occurred while updating the entries. See the inner exception for details.
SQL Server Compact timed out waiting for a lock. The default lock time is 2000ms for devices and 5000ms for desktops. The default lock timeout can be increased in the connection string using the ssce: default lock timeout property. [ Session id = 3,Thread id = 1624,Process id = 2920,Table name = JobFiles,Conflict type = x lock (x blocks),Resource = PAG (idx): 1085 ] at System.Data.Mapping.Update.Internal.UpdateTranslator.Update(IEntityStateManager stateManager, IEntityAdapter adapter)
at System.Data.EntityClient.EntityAdapter.Update(IEntityStateManager entityCache)
at System.Data.Objects.ObjectContext.SaveChanges(SaveOptions options)
at RMDataServiceLibrary.RMDatabase.Create.CreateDbJob.CreateJobFiles(Guid jobID, Dictionary`2 dictIDs) in Libraries\RMDataServiceLibrary\RMDatabase\Create\CreateDbJob.cs:line 132
after reading this i rebooted the VM and stated the Job again and this time it finished succesfully. .
i am no Windows engineer, so i do not know why this happenned but i am glad it is working again.
the above error looks like the database of OME is hanging or experiencing a lock on a talbe. is that correct interperted?