Repository edit failed | Job Refresh_ failed

Hello,

it seems that this issue is associated to region parameters, please can you check that? In the OS.

Thanks

@DELL-Marco B​ 

Hello,

Below is the region set from OS side.

Hi,

I've read that you mentioned that after the upgrade, you are not able to edit nor refresh the repository. Did it work previously in the version before the upgrade? What version is it?

Have you tried, creating a dummy repository, add a few updates and servers and test an edit? 

In the jobs option, is there any show logs to check on the failed jobs? I've downloaded the 3.4.4.908 version and tested, seems to be ok on my side, I'm not able to replicate the issue, hence not sure if there are any logs to show on the failed jobs. 

@DELL-Joey C​ 

Hello,

Before upgrade we were using the version 3.4.3.869.

Yes we tried creating dummy repository and able to edit and refresh, no errors seen.

So now the problem is withe Old repo which was created during the DRM version 3.4.3.869

Job Refresh_01/03/2024 04:53:36 completed successfully for all selected repositories.
Admin 1/3/24 4:54 AM
 Test_catalog_6525 revision is successfull
Admin 1/3/24 4:54 AM
 Job Refresh_01/03/2024 04:53:36 started.
 Repository Test_catalog_6525 edited successfully.
Admin 1/3/24 4:35 AM
 Repository with name Test_catalog_6525 created successfully.
Admin 1/3/24 4:35 AM

In the jobs option, there is no job for edit failed, how ever refresh failed ones dont have show log option, except for one refresh job.

Since new repo edit works, do we need to recreate the old repo which is not editable.

Is there any way we can edit / export and create new repo with old items?

Regards

Kalyan

Hi,

Since you are able to do the refresh and edit on a dummy repo, it means the tool is working as it should be, that rule out possibility. I suspect that some systems/products that are in the repo that you have created have been removed out from the download catalog, hence it is not able to refresh nor being edited. But that is my assumption, since the log is not available under jobs, you will need to download the log manually. It is located Help and Support menu > Save and Mail logs. You can save the logs in your local storage and check the zip file. Before you save the log, run a refresh and edit to generate new logs. Then locate filename: drmservice-0.log to check. It should give you some clues why it is failing. 

Hello, 

Thanks for the inputs, 

Checked the logs and found that DRM is unable to rename the repository version from 1.12 to 1.13

For some reason it is taking comma (,) in the place of dot . for version 1.13

And marking the refresh or edit failed.

Tried to delete old versions of repo keeping the latest.

Still edit / refresh failes.

So, up to what version a repository holds, is it till 12?

01-04-24 10:24:44 INFO com.dell.drm.service.DRMCmdExecutorTask run                                 Command obtained: com.dell.drm.repositoryhandler.DeleteRepositoryCommand@b82d24f
01-04-24 10:24:44 INFO com.dell.drm.repositoryhandler.DeleteBundlesAndComponent remove             Removing bundle/components from repository
01-04-24 10:24:44 INFO com.dell.drm.datamanager.RepositoryDataManager getCatalogFromVersion        Inside get Catalog From Version: bfb82168-3751-4242-b644-60ecc2f4cf6d 1.12
01-04-24 10:24:44 INFO com.dell.drm.datamanager.RepositoryDataManager getCatalogFromVersion        repo id: bfb82168-3751-4242-b644-60ecc2f4cf6d-1.12 Catalog fetched.
01-04-24 10:24:44 INFO com.dell.drm.datamanager.RepositoryDataManager getRepositoryByRepoNameOrId  Inside getRepositoryByRepoNameOrId for repoid bfb82168-3751-4242-b644-60ecc2f4cf6d or reponame 
01-04-24 10:24:44 INFO com.dell.drm.datamanager.RepositoryDataManager getRepositoryByRepoNameOrId  repo id: com.dell.drm.model.db.Repository@2d0fdf73
01-04-24 10:24:44 INFO com.dell.drm.datamanager.RepositoryDataManager getRepositoryByRepoNameOrId  Exiting getRepositoryByRepoNameOrId
01-04-24 10:24:44 INFO com.dell.drm.datamanager.RepositoryDataManager getSize                      Size of Repository: 987.33 MB
01-04-24 10:24:44 INFO com.dell.drm.datamanager.RepositoryDataManager createOrSaveRepository       Saving Repository Version test-Windows_allservers-all_windows_servers_:1,13
01-04-24 10:24:44 SEVE com.dell.drm.datamanager.RepositoryDataManager nextVersion                  Invalid Version Name For input string: "1,13"
01-04-24 10:24:44 SEVE com.dell.drm.repositoryhandler.DeleteBundlesAndComponent updateRepositoryVersion null
javax.persistence.PersistenceException: org.hibernate.PropertyValueException: not-null property references a null or transient value : com.dell.drm.model.db.Repository.nextrepoversion
	at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154)

Yes it is still 12.

The issue for the comma could be the fact of regional settings. 

Can you try to change it?

Hello,

Changed the region setting as below, rebooted the server too.

Still repo edit / refresh fails as below,

Could you please suggest any work around.

or

Is there any way we can recreate the same repo(which is having edit issues).

01-05-24 03:54:26 INFO com.dell.drm.datamanager.RepositoryDataManager createOrSaveRepository       
Saving Repository Version test-Windows_allservers-all_windows_servers_:1,13
01-05-24 03:54:26 SEVE com.dell.drm.datamanager.RepositoryDataManager nextVersion                  
Invalid Version Name For input string: "1,13"

Regards,
Kalyan

Hi,

You can try creating a new repo, add a simple system with an OS and update. Then use the clone menu to clone the list updates of your original repo. 

PS: I've tested the DRM for refresh version beyond .12, it is not limited. It can go beyond .12.