Installation & Licensing
Welcome to Autodesk’s Installation and Licensing Forums. Share your knowledge, ask questions, and explore popular Download, Installation, and Licensing topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error 1304 while creating a deployment

6 REPLIES 6
SOLVED
Reply
Message 1 of 7
cadfish1
633 Views, 6 Replies

Error 1304 while creating a deployment

i'm creating a deplyment out on the network but I receive the following 1304 error:

!temp1.jpg

 

I have full access rights to the root folder \\SLBF0004\Engineering\Cadapp\PDSP2013\deploy\64. 

6 REPLIES 6
Message 2 of 7
Anonymous
in reply to: cadfish1

Try a shorter path to your deployment directory. 

Message 3 of 7
dembkod
in reply to: cadfish1

Cookml,

Hello. This type of error is often due to path depth. I believe you may be running into windows depth limitations.

http://upandready.typepad.com/up_and_ready/2011/05/error-1603-and-1304-during-deployment-creation-re...

http://upandready.typepad.com/up_and_ready/2012/04/autodesk-suites-2013-deployment-path-can-easily-e...

If you shorten your deployment path you may complete.

Thank you for taking part in our community!

 

David Dembkoski

ADSK_logo_S_black_web.png 

Product Support Specialist

Autodesk Product Support



David Dembkoski
Message 4 of 7
cadfish1
in reply to: dembkod

\\slbf0004\Engineering\Cadapp\PDSP2013\deploy

 

Thanks John and David, you were right.  However my path is pretty short already.  It's difficult for me to make much shorter.  \\slbf0004\Engineering is the root on the drive which can't be changed and represent almost half the number of characters in the original path.  The remaining folder names in the part are all pretty short.  Do you have any recommendations on how I can structure the folder on this drive?

Message 5 of 7
dembkod
in reply to: cadfish1

Cadfish1,

Hello. You should be able to know with a simple test. Go shorter. \\deploy\ and try to build to this folder. Your existing path takes up 20% of the Microsoft limit currently.

 

David Dembkoski

ADSK_logo_S_black_web.png 

Product Support Specialist

Autodesk Product Support



David Dembkoski
Message 6 of 7
cadfish1
in reply to: dembkod

Are you saying the path should be \\slbf0004\engineering\deploy?  I did something similar and it worked but I can use that folder because I have several deployments (vault, acad/Inventor, algor) in both 64 and 32 bit.

Message 7 of 7
TravisNave
in reply to: cadfish1


@cadfish1 wrote:

Are you saying the path should be \\slbf0004\engineering\deploy?  I did something similar and it worked but I can use that folder because I have several deployments (vault, acad/Inventor, algor) in both 64 and 32 bit.


Don't worry about the PHYSICAL path, if you have some sort of ISO policy that designates folder locations.  You can share the last folder itself \Deploy and the UNC path will just be \\slbf0004\deploy even if the physical path location is deep like your original path.  The misconception about folder location and shares is that you have to share the top level folder and this is not correct.  Place it where you want it to go, and share the last folder.  The whole point of shares is to make it easy to get to a folder location on the network.  If you still have to traverse a million folders, you're defeating the purpose.  Share the last folder.  Problem solved. 



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Administrator Productivity


Autodesk Design & Make Report