Jartsev Posted September 3, 2009 Share Posted September 3, 2009 Instalation of the patch aborts. Message window shows "error 1316". 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted September 3, 2009 Members Share Posted September 3, 2009 Hm. That doesn't tell me much, but some have reported broken downloads (that is, their file is less than 704 MBytes). We should make sure that at least the installation file is OK. 0 Quote Link to comment Share on other sites More sharing options...
Moderators Volcano Posted September 3, 2009 Moderators Share Posted September 3, 2009 Yes, try:1) downloading the file again. 2) run the update again.As a worse case scenario, try uninstalling 2.460 and reinstalling it, then try to update it again (if it still does not work after doing #1 & #2 above). 0 Quote Link to comment Share on other sites More sharing options...
Panta Posted September 3, 2009 Share Posted September 3, 2009 Same error here, and it's still 704 MB.Cheers,Panta 0 Quote Link to comment Share on other sites More sharing options...
GH_Lieste Posted September 3, 2009 Share Posted September 3, 2009 Is it possible the new installer isn't 'foreign' character aware? That the user installation path includes characters not encoded in the 'Western/US/European' character set?I'm not saying this relates in anyway to the error reported here, but it might be worth a try to uninstall 2.460, reinstall it into a simple path with only western characters in the filename and path, and then try to update again. Small chance of any improvement I think, and it could take a couple of hours to try, but it would be faster than re-downloading a huge patch that is 'correct' only to find the same problem still exists with the replacement. 0 Quote Link to comment Share on other sites More sharing options...
raskil Posted September 3, 2009 Share Posted September 3, 2009 Is the Patch using the MSI? That sounds like the infamous "I wasn't able to remove the previous Version of this software" bug. 0 Quote Link to comment Share on other sites More sharing options...
Panta Posted September 3, 2009 Share Posted September 3, 2009 Is it possible the new installer isn't 'foreign' character aware? That the user installation path includes characters not encoded in the 'Western/US/European' character set?Why do you mean by 'foreign' characters? I am downloading from the office, we have OS in French and the error message appears at the end of the downloading. I don't feel like installing a defective patch, just to have to uninstall 2.460 and re-install it again... :sonic:btw, the 'defective download is exactly 737,676,203 bytes, or 737,677,312 bytes on disk. 0 Quote Link to comment Share on other sites More sharing options...
GH_Lieste Posted September 3, 2009 Share Posted September 3, 2009 Dunno, it was just a suggestion - accented characters, cyrillic etc. (the second failure was from Estonia). French should be within the common scheme though? So this suggestion can probably be ruled out.You say the problem occurred at the end of the process? What sections had completed at that point? (Detection/verification/copying/verification/removal)? Could it be UAC not allowing access to files marked for removal?What path is your 2.460 installed to? What windows version are you using? Is UAC turned on or off?Your file size agrees to mine, (size on disc slightly different, but that will depend on partion and file system type and size). 0 Quote Link to comment Share on other sites More sharing options...
Panta Posted September 3, 2009 Share Posted September 3, 2009 You say the problem occurred at the end of the process? What sections had completed at that point? Nyet, nyet, tovarisch, the error popup appeared at the end of the downloading process of the patch, not during its installation.And now I have re-downloaded it and no mysterious popup this time and the file has the same size...berp!Thus, I will give it a try later on, when I'll be back at the base. :debile2: 0 Quote Link to comment Share on other sites More sharing options...
GH_Lieste Posted September 3, 2009 Share Posted September 3, 2009 Good to hear, hope it goes well 0 Quote Link to comment Share on other sites More sharing options...
Jartsev Posted September 4, 2009 Author Share Posted September 4, 2009 Solved. Its was a trouble with Windows Installer, just like Raskil suggested. Solution is to uninstal 2.460 version with Microsoft Windows Installer Cleanup Utility(if normal way of deinstallation does not work), reinstal it again and apply patch. 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted September 4, 2009 Members Share Posted September 4, 2009 Ah. Excellent. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.