Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 0 subscribers
  • Views 17955 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error code 1603 installing PureMessage on Win2008 + Exchange2010

Nataku

Hi All

I'm having problems installing PureMessage on Windows 2008 R2 with Exchange 2010. I kept getting the error below and I could not figure out what is going on.

Error code 1603 was returned when running

C:\Windows\Syswow64\msiexec.exe ADDLOCAL=ClientInstall, CLientServerInstall, ServerExchangeStore,ServerInstall,ServerMain,ServerAntiSpam /qb /lvoicewarmupx! <log file name>

SETUP_INIPATH=<ini file name> REBOOT=suppress TRANSFORMS=:1033 /i C:\pmex64-401\PL\Sophos PureMessage.msi

I have tried uninstalling everything (sqlserver/av/update) then reinstall, redownload the installer (which kept giving me errors when it's decompressing - CRC error), stopping av/firewall

Any help would be great, Thanks,

:49546


This thread was automatically locked due to age.
  • 0

    UPDATE: finally managed to get the installer to install MSSQL server on it's own, but the databases are not being created, suspecting this is because of rights of the user accounts but I have tried giving MSSQL$SOPHOS/MY_ACCOUNT full rights to the database... any idea if there is any way or script I can use to get the 4 dbs created?

    :49588
  • 0

    Hi Nataku,

    The problem may not be as simple as the databases not being created by the installer. Generally, most install problems are related to local environment issues, unless there's a clear error in one of the install logs then you'll need to raise a support case as extra logging will be required and the resultant errors will need to be investigated.

    Regards,

    Reginald

    :49602
  • 0

    Thanks Reginald, I was planning on giving them a call today too (edit, different account)

    :49618
  • 0

    So I have contacted support and provided them with logs. They were pretty quick to reply and have found the problem.

    The extra logs were showing login denied with the SophosPureMessage account. I found out after asking around that our password complexity check has been raised and caused the default password we use for these system accounts to fail. (it still works for log in, just not setting) So for some reason PureMessage installation requires setting the password again even if the account already exists.

    This won't fix every error code 1603, but it's worth trying if you are running into the same error code as I do. (for anyone that is searching for a fix for this error)

    :49742
  • 0

    Hello Nataku,

    This won't fix every error code 1603

    More than correct - indeed 1603 is a generic error code usually indicating you have to look elsewhere (the extra logs - e.g. from a CustomAction) for the actual error.

    Christian

    :49786
Unfiltered HTML