Jump to content

Windows File Server install failing


Recommended Posts

Hello,

 

What causes Windows File Server install to fail with:

 

MSI © (58:54) [15:41:50:461]: Doing action: InstSuppPrepareInstall
Action 15:41:50: InstSuppPrepareInstall. 
Action start 15:41:50: InstSuppPrepareInstall.
MSI © (58:AC) [15:41:50:461]: Invoking remote custom action. DLL: C:\Users\ADMIN\AppData\Local\Temp\2\MSI7D25.tmp, Entrypoint: caPrepareInstall
ESET: Entering CA InstSupp!caPrepareInstall (limited: no)
ESET: Returing from CA InstSupp!caPrepareInstall with status 1627 (duration: 0.0)
CustomAction InstSuppPrepareInstall returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 15:41:50: InstSuppPrepareInstall. Return value 3.
MSI © (58:54) [15:41:50:476]: PROPERTY CHANGE: Deleting RESUME property. Its current value is '1'.
MSI © (58:54) [15:41:50:476]: PROPERTY CHANGE: Deleting Resume property. Its current value is '1'.
MSI © (58:54) [15:41:50:476]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI © (58:54) [15:41:50:476]: Doing action: FatalError
Action 15:41:50: FatalError. 
Action start 15:41:50: FatalError.
DEBUG: Error 2826:  Control BottomLine on dialog FatalError extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalError, BottomLine, to the right
Action 15:41:50: FatalError. Dialog created
MSI © (58:A4) [15:41:50:492]: Note: 1: 2205 2:  3: _RemoveFilePath 
MSI © (58:A4) [15:41:50:508]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.
MSI © (58:A4) [15:41:50:508]: Note: 1: 2205 2:  3: BindImage 
MSI © (58:A4) [15:41:50:508]: Note: 1: 2205 2:  3: ProgId 
MSI © (58:A4) [15:41:50:508]: Note: 1: 2205 2:  3: PublishComponent 
MSI © (58:A4) [15:41:50:508]: Note: 1: 2205 2:  3: Extension 
MSI © (58:A4) [15:41:50:508]: Note: 1: 2205 2:  3: Font 
MSI © (58:A4) [15:41:50:508]: Note: 1: 2205 2:  3: Class 
MSI © (58:A4) [15:41:50:508]: Note: 1: 2205 2:  3: TypeLib 
MSI © (58:A4) [15:41:50:508]: Note: 1: 2727 2:  
MSI © (58:B8) [15:41:52:774]: PROPERTY CHANGE: Deleting SHOW_KB_PAGE property. Its current value is '1'.
MSI © (58:B8) [15:41:53:493]: PROPERTY CHANGE: Adding CustomActionData property. Its value is 'RESTART_REGISTERED'.
MSI © (58:B8) [15:41:53:493]: Doing action: InstSuppReadProperty
 
Thank you
 
Gert
Link to comment
Share on other sites

Found the solution, going to use ERA5 until I find a new AV product that's not a nightmare to use. Something that makes my life simpler, not harder.

 

After testing ERA6, I can honestly say that compared to ERA5, it is horrible and buggy. Customer experience - it's been almost two days since I touched it and I still wake up pissed off.

Link to comment
Share on other sites

  • Administrators

Please elaborate more on what you consider buggy. ERA v6 has no known serious bugs and if one's having issues with it it's mainly due to misunderstanding of how the new version works. ESET has created a lot of knowledgebase articles and videos to address questions and common issues reported by users. Also this forum is monitored by developers who provide answers to tough or complex questions.

Link to comment
Share on other sites

I've always liked Eset, it's products and customer service. But, you should really take ERA6 behind the building and shoot it in the head (twice if possible) and release ERA5.5. 

 

Knowledgebase articles and videos are all nice, but consider this - when using ERA5 I didn't have to spend my days reading knowleadgebase articles and watching videos, it worked and was simple and intuitive. This is why ERA6 is bloody horrible - _ it is too complex and getting it to work and managing it takes too much of my time_. Period. 

Link to comment
Share on other sites

  • ESET Moderators

Hello Gert,

 

thank you for your feedback.

 

The product is indeed different from ERA v.5 as we designed and made it from a scratch.

For the people who never used ERA at all the version 6 seems much more intuitive to use.

 

The architecture is bit more complex, but it allows us to do things, which were not possible before like the product is now platform independent.

 

The ERA v.6 is really getting better over time (we are adding new features, incorporating feedback from customers and partners, improving usability, fixing bugs) so stay tuned for next release(s).

 

Regards,

 

P.R.

Link to comment
Share on other sites

  • 1 year later...

Found the solution, going to use ERA5 until I find a new AV product that's not a nightmare to use. Something that makes my life simpler, not harder.

 

After testing ERA6, I can honestly say that compared to ERA5, it is horrible and buggy. Customer experience - it's been almost two days since I touched it and I still wake up pissed off.

 

 

I've always liked Eset, it's products and customer service. But, you should really take ERA6 behind the building and shoot it in the head (twice if possible) and release ERA5.5. 

 

Sadly, but true ... :angry:

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...