Software Deployment

ORIGINAL: ogeccut
Created a log after install failed installing symantec 11.
Info 1923.Service Symantec Event Manager (ccEvtMgr) could not be installed. Verify that you have sufficient privileges to install system services.
Action ended 16:27:29: InstallFinalize. Return value 3.
Running install under full admin account.
What could be the problem?


You need to contact Symantec.
Try running it under a different admin account (local admin maybe?) and see if that works.
You're not trying to repackage this are you? If you are, don't. It won't work.

Not repackaging. Been contacting symantec for a long long, very long time. Ran it under local admin and domain admin.

Thanks for the answer.

sorry i can't help but appears to be vendor problem, not one related to deployment or packaging. Any indication why Symantec are so unresponsive? Tell them your entire company is going to switch to Mcafee, Trend Micro or Sophos if you can't get this resolved. That'll get their attention.

BTW, 1923 is a service related MSI error so it appears to be (partly at least) an MSI installation. Probably extracted out of the EXE and then run.

Can anyone guess what my suggestion is going to be? Do we imagine it might, just might, involve the use of ProcMon? I guess you were all leaving it to me, right?

Tried contacting Symantec and got the worst support imaginable. Tech tried to blame the issue on everything but Symantec.
Asked for escalation for a week and was told there is no way to escalate it; they don’t have next level support. Manager either not in today or not available at the moment. After 3 weeks on the phone finally got to advanced team. Trying to find the solution myself and will propose to switching to other product.

ORIGINAL: ogeccut
Running install under full admin account.

What could be the problem?Run your install in parallel with ProcMon: it *will* tell you what the problem is, i.e. what registry/file access has been denied. You can then investigate that registry key or file's permissions.

It's an unfortunate truism these days that unless you have mortgaged three generations of your family to a Gold support contract, vendor support will be next to useless (and even then is probably of dubious value.) Simply put, they are not interested in your problems. They make all the right noises, of course, but in practice, they just wish you'd go away.

Ran install with ProcMon, not sure what to look for. There is no ACCESS DENIED, since testing under local admin. Getting a lot of "NO MORE FILES, NO MORE ENTRIES, NOT EMPTY, NAME NOT FOUND, PATH NOT FOUND" Is there any documentation on procmon results column?
Thank you.

Procmon probably isnt going to be much help with this problem. You already know what service is failing to install. ccEvtMgr.
Although in saying that, it could be a permissions problem on a file or registry.
Are you doing an upgrade ? An older version was installed ?
Ive seen the same error with a different app, when the older version didnt uninstall properly.
Error 1923 occurs because the installer cant access something, ie. create a service because it is already installed and started.

my 2 cents worth.

ORIGINAL: ogeccut

Ran install with ProcMon, not sure what to look for. There is no ACCESS DENIED, since testing under local admin. Getting a lot of "NO MORE FILES, NO MORE ENTRIES, NOT EMPTY, NAME NOT FOUND, PATH NOT FOUND" Ignore 'NO MORE FILES, NO MORE ENTRIES, NOT EMPTY' - they're normally the result of file/folder/registry enumerations.

'NAME NOT FOUND, PATH NOT FOUND' is more where you should be concentrating, although many of these will be kind of spurious, especially if you have a long PATH statement. Hopefully, it's obvious that, if an app tries to open, say MSCOMCTL.DLL which normally lives in %SystemRoot%\SYSTEM32, it starts in its own directory (NAME NOT FOUND), then it starts walking the PATH - C:\ (NAME NOT FOUND) C:\WINDOWS - or whatever %SystemRoot% resolves to - (NAME NOT FOUND), C:\WINDOWS\SYSTEM32 (NAME NOT FOUND)....I'm sure you get the idea.

As soon as the error appears, switch to ProcMon and look at the last few pages of output. Don't forget you can filter out a lot of the junk and filters can be saved for future use. For example, I filter all the crap to do with Windows opening Control Panel registry entries; all the a/v processes; Explorer.EXE...

Is there any documentation on procmon results column?None that I know of. It'll become easier with usage. I honestly believe you cannot do this job without it (or similar tool) so best get used to it! :)

Are you doing an upgrade ? An older version was installed ?
Yes, i have 10 client installed and "upgrading" trying to, client 11. Friday night was promised a call back Monday morning from Symantec, no calls yet.