When I try and re-import from an exported permissions excel file, projectWise returns me the error message `Unable to import from excel. Make sure Excel 2003 or newer is installed'. I have installed office 2010 and 2016 and get the same result, I have tried importing the xlsx and the csv and I get the same result. I have attempted to do the import using ProjectWise V8i and ProjectWise CONNECT and I get the same result.
#can successfully export the access control to xlsxExport-PWAccessControlToExcel -ExportFolder $Path -ExportFileName "H999995_accesscontrol" -InputFolder $ProjectToArchive -AllLevels
#can successfully export the access control to csvExport-PWAccessControlToExcel -ExportFolder $Path -ExportFileName "H999995_accesscontrol" -InputFolder $ProjectToArchive -ExportFileExtension 'csv' -AllLevels
#unable to import the access control from xlsxImport-PWAccessControlFromExcel -ImportFileNamePath 'C:\temp\Export\PWArchive\H999995_accesscontrol.xlsx' -InputFolder 'Projects\Hatch Internal\SiteABC\H999995'
#unable to import the access control from csvImport-PWAccessControlFromExcel -ImportFileNamePath 'C:\temp\Export\PWArchive\H999995_accesscontrol.csv' -InputFolder 'Projects\Hatch Internal\SiteABC\H999995'
Kind regardsGavin Chapman
I'm not sure which versions of ProjectWise and Office are currently supported, but in the past if you weren't using one of the unsupported versions of Office that message would show up, even if your Office version was newer than the indicated version. It really should have said, "Only Office 2003 and Office 2007 are supported." That was changed at some point in recent years, for at least some of the utilities that leverage Office.
I don't really want to go and install an old Office 2007, and I am sure that in the SIG demo that office 2016 was said to be supported, it seems that my problem might not be with the PowerShell DAB that I downloaded, but rather with ProjectWise explorer since I cant even do the import manually through the explorer.
this could also mean the excel file is corrupt. Can you export a new one?
Answer Verified By: GChapman
So it turns out that when exporting and re-importing on the same datasource, then the access control import permissions works fine. but when exporting from one datasource and importing to another datasource, that's when the access control import permissions gives the error, thank you all for your input into tracking down the problem.
You will need to ensure all users/groups/userlists exist within the secondary datasource. If they do not, the import will fail.
I got this same error message while importing Access Control. It turned out that one of the states in the workflow had been renamed slightly after the Access Control had been exported and so it must have confused ProjectWise when importing. I updated the spreadsheet to match the new state name and it imported fine. This error message is maybe a bit misleading.
Answer Verified By: Brian Flaherty
my top tip for this error message since it has to be one of the most unhelpful PW error messages and I think we can probably all agree there are a lot of unhelpful PW error messages out there.
Check your pwc.log file, it often tells you why it can't do the import, believe me that has saved me hours of searching through those spreadsheets for the slightest error because it could be anything from a badly named workflow state to a spelling mistake in a folder name etc.