Installation & Licensing
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Re: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Do you mean recreate from scratch from the media? I tried that several times now and the result is the same. I was hoping there is some silver bullet to get it to work. Network folder permissions are good (I'm even trying to install as a domain admin, so that shouldn't matter anyway).
Re: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
yes, re-create from scratch. The only other issue I had occured because I was trying to install a 32-bit verion on a 64-bit OS.
Re: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I actually just created the deploy right on my extra drive on my workstation and then ran the installer and it worked! So it has to be something with the server, maybe the path becomes too long or too deep at some point?
Has anyone else had to put their deploys near the root of a network drive in order for it to work?
Re: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
That's almost certainly the reason for your failure. Folder depth and 255 character path limit is a real problem with deployments. That is why your UNC share path should always be \\SERVERNAME\SHARENAME
If you share it like that, you'll probably have better success.
My Expert Contributions to the Discussion Groups: FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files | Disk Space
If my post was helpful, please give Kudos and/or mark the Accept as Solution button(s) below. Thank you!Re: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
That does appear to be the problem so I will be creating the deploys as close to the root of the share as possible and not nesting it deeper in as in the past.
Thanks!
aRe: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I was having the same problem until a ran the Create and Modify a deployment. I kept the silent install checked but removed the other two checks ( can't remember what they were, something about creating log files). After this, the deploy went smoothly. In my opinion, it has something to do with not having appropriate permissions to write the log file on the deployment server...
Hope this helps...
Re: aRe: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
The silent option doesn''t seem to matter for me (yet-hopefully not) and so far, everything is working good by creating the deploys on a network share that isn't nested very deep.
One thing I did notice is that sometimes the setup.exe stops moving along after clicking through the create deploy dialogs, just before it gets to the dialog where you select the products to include. I found that by using Resource Monitor to suspend setup.exe and then resuming it, it continues to the product selection dialog window.
Re: aRe: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
sysbackup wrote:I was having the same problem until a ran the Create and Modify a deployment. I kept the silent install checked but removed the other two checks ( can't remember what they were, something about creating log files). After this, the deploy went smoothly. In my opinion, it has something to do with not having appropriate permissions to write the log file on the deployment server...
Hope this helps...
You'll want to make sure that your deployment share has full write access on both the share and the folder permissions. I typically set the everyone account to full control. The UNC should always be \\servername\share even in the folder structure of the physical location is deeper. This will prevent folder depth / filepath length issues.
My Expert Contributions to the Discussion Groups: FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files | Disk Space
If my post was helpful, please give Kudos and/or mark the Accept as Solution button(s) below. Thank you!Re: aRe: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
I checked perms when I first had problems and they are set up like you mentioned. I appreciate the feedback from everyone! So far, everything from creating deploys to running them work great!
Re: aRe: 2013 Install Process
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Hi TravisNave,
Is this to create a folder under this: \\servername\share is a must? I currently also facing this issue on creating this deployment on 2 different networks. The one created in this \\servername\share worked, but the other failed.
Just wonder this is just a coincident or due to others reason. Thanks.


