You install is failing because you are using Shared Content with Revit, but are trying to use a mapped drive letter instead of a UNC path.
Error from your log file:
MSI (s) (AC:30) [16:32:59:099]: Product: Revit 2014 - - Error 1327.Invalid Drive: V:\
In Windows 7 or 8 with UAC on if a drive is mapped from a command prompt, like via a log in script, the drive won't be availabe in Windows Explorer so the install of Revit doesn't know the drive exists.
Check out my last post for this previous discussion.
Thanks for responding. My appoligies, that was the install log from a machine I manually installed Revit. Attached is the log file from a machine i just tried to deploy 2 a few minutes ago and it failed. if you could assist that would be great. Thank you.
It looks like I might have the same mapped drive issue for shared content. Will try and edit the deployment to use UNC paths and try again.
Danny, thank you for the response and help.
We turn UAC off on every machine here and it is currently off on mine as well. I am using Shared Content, but the only place I am referencing our "V" drive is in the Revit directory locations. I am also unchecking all content as part of the deployment since I don't want every install to attempt to install the content to the shared location (it already exists there), unless I am misunderstanding the process.
I can try to use UNC pathing to see if that fixes the problem, but would rather not. We have always use drive mappings in the past with no problems.
I agree that drive mappings are severely problematic and UNC pathing should always be used.
You problem may be a corrupt deployment, looks like the install is having probelms accessing some files from your deployment.
From the log file:
MSI (s) (2C:4C) [10:44:40:822]: Product: Revit Architecture 2014 - - Error 1309.Error reading from file: \\GWWO7\PCSetup\Autodesk\Deployments\RAC 2014\Img\x64\RAC2014\Program Files\Autodesk\Root\Textures\Reflect.exr. System error 64. Verify that the file exists and that you can access it.
Check the textures folder to make sure the file exists, but you may need to recreate the deployment.
Bob and cstarr,
You both have something in common with your deployments. Both of you have spaces in your deployment path (deployment root directory):
Modify the deployment folders, shortcut paths and INI files to exclude the space a run the deployment again.
It takes a little bit of scripting to automate but you could also specify Shared folder locations to a dummy folder on your C drive and then edit "C:\ProgramData\Autodesk\RVT 2014\UserDataCache\Revit.ini" replacing the dummy folder for your mapped network drive locations. Like replacing C:\Dummy\ in C:\Dummy\IES with Z:\Revit_2014\ to get Z:\Revit_2014\IES. You have to make sure you make the adjustment before anyone runs Revit on that computer.
You can't just switch it out for a Revit.ini file of your liking because the InstallGUID line may be different.
I'm not entirely sure what solved the issue but between using UNC paths in the deployment and taking the spaces out of the directory/file names, the deployment started working properly wihtout disabling UAC.
Thank you for your assitance.
Access a broad range of knowledge to help get the most out of your products and services.