Unsolved
1 Rookie
•
11 Posts
0
83
Repository edit failed | Job Refresh_ failed
Hi Team,
After the upgrade to verison Version 3.4.4.908. We unable to edit the Repositories, or refresh the same.
Getting the error as attached in the screenshot.
* Already tried clean uninstall and re install of the application, Reboots.
* NT AUTHORITY\LOCAL SERVICE has access to the DRM folders, (program files, programdata )
Could you suggest some solution for this.
DELL-Marco B
Moderator
Moderator
•
3.5K Posts
0
January 2nd, 2024 18:43
Hello,
it seems that this issue is associated to region parameters, please can you check that? In the OS.
Thanks
_Kalyan_
1 Rookie
1 Rookie
•
11 Posts
0
January 3rd, 2024 03:14
@DELL-Marco B
Hello,
Below is the region set from OS side.
DELL-Joey C
Moderator
Moderator
•
3.3K Posts
0
January 3rd, 2024 09:48
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.
_Kalyan_
1 Rookie
1 Rookie
•
11 Posts
0
January 4th, 2024 03:13
@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
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
DELL-Joey C
Moderator
Moderator
•
3.3K Posts
0
January 4th, 2024 07:53
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.
_Kalyan_
1 Rookie
1 Rookie
•
11 Posts
0
January 4th, 2024 09:39
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?
(edited)
DELL-Marco B
Moderator
Moderator
•
3.5K Posts
0
January 4th, 2024 17:25
Yes it is still 12.
The issue for the comma could be the fact of regional settings.
Can you try to change it?
_Kalyan_
1 Rookie
1 Rookie
•
11 Posts
0
January 5th, 2024 03:28
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).
Regards,
Kalyan
(edited)
DELL-Joey C
Moderator
Moderator
•
3.3K Posts
0
January 5th, 2024 09:45
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.