Upgrading PLESK 8.2 to 8.3 and receiving Error 1713

[grfecom]

I was wondering if anyone is experiencing any problem during the process of upgrade from PLESK 8.2 to 8.3. I receive Error 1713 upon starting the installation process. My server is Win2003 and II6. I was thinking maybe I need to have Windows 2008 and IIS7 for PLESK 8.3! Any help is much appreciated.

Product: Plesk 8.3 for Microsoft Windows -- Error 1713. Plesk 8.3 for Microsoft Windows cannot install one of its required products. Contact your technical support group. System Error: 1605.

The screen capture of the error message is attached this thread for your info.

 

[grfecom]

Any success story/experience from anyone upgrading from earlier versions of PLESK to 8.3 on Windows 2003 Server Enterprise Edition?

 

[grfecom]

Apparently the problem's caused by a missing windows installer cache for one of the parts of plesk. Anyone has any idea about that missing file?

Related thread here: http://forum.swsoft.com/showthread.php?t=50076

 

[grfecom]

anybody, any idea?!! I still looking for a solution. SwSoft support doesn't answer! Why?!

 

[tomoiaga]

Look at the Event Viewer after you get the error message, maby there is more there.
regarding your request to swsoft for support dont't get me started about SWSoft and Plesk.
grfecom, you may get lucky with 8.3 but after everything I've been through, I suggest that you keep 8.2 for a while and let othe people test it.

 

[grfecom]

That's right. I agree!

However, about the error message. I did check the event viewer and it clearly states the error, but there is no enouygh info to find the solution. Here is what log says:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11713
Date: 1/5/2008
Time: 10:11:26 AM
User: MADISON\Administrator
Computer: MADISON
Description:
Product: Plesk 8.3 for Microsoft Windows -- Error 1713. Plesk 8.3 for Microsoft Windows cannot install one of its required products. Contact your technical support group. System Error: 1605.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 45 31 39 35 44 43 32 {E195DC2
0008: 36 2d 41 36 42 34 2d 34 6-A6B4-4
0010: 45 31 33 2d 42 38 45 39 E13-B8E9
0018: 2d 44 36 31 42 34 33 39 -D61B439
0020: 39 37 44 44 44 7d 97DDD}

Any thoughts?

 

[Bender]

Hi,

Run installer with logging to find out what component brake the upgrade:

plesk_8.3.0_build071225.14.msi /l*v <log file>

 

[grfecom]

Bender,

Many thanks for your great suggestion. It worked very good; however, I have no idea that what is causing that. When I review the log file, everything seems to be fine except the last few lines which halts the installation process.

I'm copying the last section here for you and will be very thankful if you could give me your idea.

=== Logging stopped: 1/6/2008 20:56:40 ===
MSI (c) (D0:F0) [20:56:40:694]: Note: 1: 1729
MSI (c) (D0:F0) [20:56:40:694]: Product: Plesk 8.3 for Microsoft Windows -- Configuration failed.
MSI (c) (D0:F0) [20:56:40:710]: Attempting to delete file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\2d3f1412.msp
MSI (c) (D0:F0) [20:56:40:710]: Attempting to delete file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\2d3f1412.msp
MSI (c) (D0:F0) [20:56:40:710]: Unable to delete the file. LastError = 2
MSI (c) (D0:F0) [20:56:40:710]: Attempting to delete file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\2d3f1413.mst
MSI (c) (D0:F0) [20:56:40:710]: Unable to delete the file. LastError = 32
MSI (c) (D0:F0) [20:56:40:725]: Grabbed execution mutex.
MSI (c) (D0:F0) [20:56:40:725]: Cleaning up uninstalled install packages, if any exist
MSI (c) (D0:F0) [20:56:40:725]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/6/2008 20:56:40 ===

 

[botsman]

Bender,

Many thanks for your great suggestion. It worked very good; however, I have no idea that what is causing that. When I review the log file, everything seems to be fine except the last few lines which halts the installation process.

I'm copying the last section here for you and will be very thankful if you could give me your idea.

Try to apply this swsoft KB article to fix the issue:

http://kb.swsoft.com/en/1863