- Joined
- Dec 6, 2007
- Messages
- 261
- Reaction score
- 1
Hi,
When upgrading from v5.0.3563.0 to v5.0.3647.0 (via the Versions/Updates section in the management console) I get the following error dialog box pop up:
---
3CX Phonesystem 5.0 Setup
Error opening file for writing:
C:\Program Files\3CX PhoneSystem\Bin\xerces.dll
Click Abort to stop the installation, Retry to try again, or Ignore to skip this file
---
I can't Retry, and Ignoring moves the error message onto zlib1.dll in the same folder, and then 3CXSMTP.dll, libpq.dll, cornerr32.dll, krb5_32.dll, libiconv-2.dll, libintl-2.dll, ssleay32.dll, libeay32.dll, and then it continues onto the copying to the recordings folder, does some more installing, and then comes up with the same error, but for 3CXFaxServer.exe. Ignoring that one gets you to the end of the install where it asks you to reboot.
Any ideas?
(This is a server dedicated to testing 3CX. It's a Dell Dimension 5000 running Server 2003, fully patched, with no other non-Microsoft software on it. It was originally installed with v3, then v5.0.3647.0, and now v5.0.3563.0 - so it should in theory be an error most people would come across??)
When upgrading from v5.0.3563.0 to v5.0.3647.0 (via the Versions/Updates section in the management console) I get the following error dialog box pop up:
---
3CX Phonesystem 5.0 Setup
Error opening file for writing:
C:\Program Files\3CX PhoneSystem\Bin\xerces.dll
Click Abort to stop the installation, Retry to try again, or Ignore to skip this file
---
I can't Retry, and Ignoring moves the error message onto zlib1.dll in the same folder, and then 3CXSMTP.dll, libpq.dll, cornerr32.dll, krb5_32.dll, libiconv-2.dll, libintl-2.dll, ssleay32.dll, libeay32.dll, and then it continues onto the copying to the recordings folder, does some more installing, and then comes up with the same error, but for 3CXFaxServer.exe. Ignoring that one gets you to the end of the install where it asks you to reboot.
Any ideas?
(This is a server dedicated to testing 3CX. It's a Dell Dimension 5000 running Server 2003, fully patched, with no other non-Microsoft software on it. It was originally installed with v3, then v5.0.3647.0, and now v5.0.3563.0 - so it should in theory be an error most people would come across??)