Internal Error 2705 Directory Wise Installer
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework http://www.symantec.com/connect/blogs/why-we-get-internal-error-2705-directory-error-during-msi-installation and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Wise Solutions: Wise Installer Forum http://www.tek-tips.com/viewthread.cfm?qid=581439 at Tek-Tips HomeForumsProgrammersDevelopment ToolsWise Solutions: Wise Installer Forum Internal Error 2705 thread772-581439 Forum Search FAQs Links MVPs Internal Error 2705 Internal Error 2705 harryn4484 (Programmer) (OP) 19 Jun 03 21:44 I am getting "Internal Error 2705 - Directory" if I try to test an install set within Wise 3.5 for windows or on any install set I create and run on other machines. Does anybody know what is causing this?Thanks RE: Internal Error 2705 RobSchultz (Programmer) 25 Jun 03 08:43 The 2705 error means you have an directory that "can't be linked as tree".Look at the directory table directly (Setup Editor -> Tables) and see if any are highlighted red.If so, then fix the problem.If not then run your install with the following command line: msiexec /I "full path to msi" /L*V c:\install.logThis will write and install log that may point you in the right direction as all directories used in the insta
for the community · Log in · Help ForumsCategoryBoardDocumentsUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results http://forums.ni.com/t5/Measurement-Studio-for-NET/InstallShield-installation-Error-2705/td-p/243858 by suggesting possible matches as you type. Showing results for Search instead for https://blogs.msdn.microsoft.com/smondal/2012/01/13/ms11-100-kb2656353-error-microsoft-net-framework-1-1-internal-error-2705-directory/ Did you mean: Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page All Forum Topics Previous Topic Next Topic « Previous 1 2 3 4 Next » InstallShield installation - Error 2705 InstallShield installation internal error - Error 2705 Chris Williams… Member 07-20-2005 09:37 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hi, I am using the following setup: Product: NI Measurement Studio 7.1 Installer: Installshield Professional 10.5 with SP1 When I try to include merge modules for Measurement Studio Winforms classes into my installation I see error internal error 2705 2705-Directory. For some setup configurations this was shortly followed by errors 2731.0 and/or 2732.0. I have confirmed that the ProgramFilesFolder directory entry is present as per the advice in the Knowledgebase. After some experimentation I have managed to discover the following: 1) The problem occurs for InstallScript MSI projects, but not for Basic MSI projects. However we need installscript functionality in order to install our application. 2) The problem can be reproduced using a very basic InstallScript MSI project. After creating the project, "NIMesaDLL" was selected from the redistributables panel window. This in turn caused it's "NI Installer Utilities" and the "Microsoft C Runtime Library 6.0" to be selected. The release wizard was used to create an uncompressed setup, with both the MSI engine and the installscript engine extracted from setup.exe. The resulting setup program failed with error 2705 3) If the above setup is changed to be compressed, error 2732 can also be seen. I would have given you the entire installation log, but I appear to be limited to 5000 characters. Here's the final section of the log, including both errors. Property(S): SOURCEDIR = C:\DOCUME~1\wilchr\LOCALS~1\Temp\_is7D\ Property(S): SourcedirProduct = {E3F3
2705. Directory ★★★★★★★★★★★★★★★ Soumitra MondalJanuary 13, 201220 Share 0 0 The recent release of Microsoft Security Bulletin MS11-100 KB2656353 might fail on Windows XP/Windows 2003 systems. The patch may fail with an error message: “Microsoft .NET Framework 1.1 -- Internal Error 2705. Directory” In fact, if you try to repair existing .Net Framework 1.1, you would receive the same error message: “Microsoft .NET Framework 1.1 -- Internal Error 2705. Directory” The above error message indicates that there is a directory tree definition problem on the machine (a directory references a parent that isn’t defined). After digging it further, I found why the failure is happening. The root cause is that KB2656353 requires .Net Framework 1.1 SP1 to be registered against the .Net Framework 1.1 product, but it was not. Even though Microsoft .Net Framework 1.1 SP1 may appear in add/remove programs, it may not be registered. To determine if SP1 is registered check the install log. As per the install LOG: We do not see the 1.1 SP1 patch in the sequence. MSI (s) (7C:1C) [15:58:37:948]: Final Patch Application Order: MSI (s) (7C:1C) [15:58:37:948]: {2A3320D6-C805-4280-B423-B665BDE33D8F} - MSI (s) (7C:1C) [15:58:37:948]: {EFCE7BE0-510E-4932-9475-F44CD90DE16A} – .Net 1.1 SP1 is {411EDCF7-755D-414E-A74B-3DCD6583F589} and is missing from this list. Resolution: Just installingMicrosoft .Net Framework 1.1 SP1 patch should resolve this issue. Please install Microsoft .Net Framework 1.1 SP1 http://www.microsoft.com/download/en/details.aspx?id=33 on the system and then install KB2656353. Comments (20) Cancel reply Name * Email * Website Nath says: January 13, 2012 at 8:16 am Many thanks, the problem is solved. Reply Claire Martine says: January 14, 2012 at 12:09 pm Thank you very much, this posting was clear and concise, beyond helpful! Problem solved in no time! Reply Nitish says: January 17, 2012 at 4:42 am Awesome article Reply Joe says: January 17, 2012 at 8:47 pm So how do you resolve this when you have thousands of computers with this issue and relying on WSUS?