Trying to restore Jira Software from a backup zip

[Mike Taylor]

While trying to upgrade Service Management using the installer, the process failed, after deleting most of the Jira directory. The Windows Service was also removed as part of the process.

I am now trying to unzip the backup file to restore the Jira directory to its previous state, and I have 2 issues:

1) I cannot copy UserSearchServiceStatsData$Optimised$FindTopUsersInternal$FindTopUsersWithPermissionInIssueFromGroups$FindTopUsersWithNameInGroups$QueryDslJiraCrowdDAOSettings.class to its original location due to the file path being too long. This was zipped in place, and worked with this exact length previously. 

2) The Windows service is missing, and I do not know how to reinstall just the service, oir repair the installation effectively.

[Andy Rusnak]

Hi Mike, 

I am sorry to hear about the difficulties you are having restoring your Jira Server. 

1. Windows as a hard limit of 255 characters for a full file path.  Where is this file attempting to be unzipped to?  The file name you included is only ~160 characters, so it should be possible to have another 95 characters in the file path before you run into the limit.  
   1. What unzip utility are you using?  I have seen this type of issue occur with the built in standard Windows compression utility with other zip files, it can often times be resolved by using something like 7Zip.  
2. In terms of reinstalling the Jira Windows service, that can be done manually using the service.bat utility within the Jira install directory.  Additional information/steps to running this utility and setting the service up to run automatically can be found at the following link: Running Jira Applications As A Windows Service .  About half way down the page it will discuss the manual installation options. 

Best, 

Andy

[Andy Rusnak]

Hi Mike, 

I just wanted to follow up really quick as I came across a setting that might be helpful for you.  I wasn't aware this was added to Windows, but starting in Windows 2016/Windows 10 and higher, you can actually set the OS to allow for longer than 260 character paths, but you have to opt into this behavior.  

The following link from Microsoft elaborates on this functionality: Maximum File Path Limitation 

Enabling this option may resolve for your question as well if the root cause of that message is that the file path is too long.  

Before making any changes to these keys, I would recommend testing this on a non-production server just to confirm there isn't any unexpected behavior.  

Best, 

Andy