Hi Frank,

Thanks for starting a good discussion.  I would recommend everyone thinking about ugprading to Symantec Brightmail Gateway (SBG) version 9.0.0-20 to take a look at the following information before upgrading to avoid any potential issues:

a) SBG 9.0 Release Notes:
http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

b) How to ensure there is appropriate access from the Symantec Brightmail Gateway scanner to the configured LDAP servers.
http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

c) the Software Update Notes within the Control Center (Administration > Version > Updates > View Description )

Regards,

Adnan

LDAP has moved from a Sync, to dynamic queries from each appliance.  So DMZ scanners will need LDAP access to an inside LDAP source, instead of just the Control Center.   Also, you can move to LDAP over SSL, and that will require firewall changes as well.

See also this posting:

"SBG 8.0.3 upgrade to 9.0-20 failure - Error During Software Update: An error has occurred during software update. Err Inappropriate ioctl for device..."
http://www.symantec.com/connect/forums/sbg-803-upgrade-90-20-failure

We successfully updated from 8.0.3 to Version 9 with no problems.

Details:
Running on VMware ESX 3.5 Update 4
2 Scanners and 1 Controlcenter & Scanner

Anyone looking to upgrade to version 9.0 should first look at the updated KB artilce about this known issue:

http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

and the Updated Release Notes (paying special attention to Known Issues):

http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

Regards,

Adnan

I am having probles after the upgrade. After backup up BMG 8 I copied it to antoher compuer. Then I go in through CC  and find the upgrade. Afterwards it downloads and updates then wihen it restart, it won't boot anymore. Anyone else have this problem?

Uh oh, time for an OSrestore :(

It happens to the best of us. If you need to download the 8.0.3 ISO you'll want to visit https://fileconnect.symantec.com. Use Serial number TMP58392128 if you can't locate your serial number.

Once you reinstall 8.0.3, just restore to your backup file and try the upgrade again. Make sure to follow the steps in this document to avoid this in the future:

Title: 'How to upgrade a Symantec Mail Security Appliance or Symantec Brightmail Gateway to its latest release'
Document ID: 2006110911420963
> Web URL: http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

After upgrading from 8.0.3 to 9.0.0, the error message appears when accessing to Aliases in Protocols > SMTP as displayed below.

Application Error       The application encountered an error. If you are the administrator, please check the log files for details.         Click here to return to the previous page Click here to return to the login page

class java.util.NoSuchElementException: null at java.util.ArrayDeque.removeFirst(Unknown Source) at java.util.ArrayDeque.pop(Unknown Source) at com.brightmail.util.BrightmailDepthFirstSearch.runDfs(BrightmailDepthFirstSearch.java:154) at com.brightmail.util.BrightmailDepthFirstSearch.isCyclicDfs(BrightmailDepthFirstSearch.java:84) at com.brightmail.bl.setting.AliasSettingsManager.isCyclicReferenceDetected(AliasSettingsManager.java:566) at com.brightmail.pl.flow.setting.AliasFlow.list(AliasFlow.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.brightmail.pl.flow.CommandFlow.execCmd(CommandFlow.java:267) at com.brightmail.pl.flow.CommandFlow.execCmd(CommandFlow.java:232) at com.brightmail.pl.flow.CommandFlow.service(CommandFlow.java:172) at com.brightmail.pl.flow.FlowServlet.service(FlowServlet.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.brightmail.pl.filter.AdministratorRoleChecker.doFilter(AdministratorRoleChecker.java:207) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.brightmail.pl.filter.SessionChecker.doFilter(SessionChecker.java:130) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.brightmail.pl.filter.CacheBuster.doFilter(CacheBuster.java:93) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.brightmail.pl.filter.CharacterEncoder.doFilter(CharacterEncoder.java:93) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.brightmail.pl.filter.HostACL.doFilter(HostACL.java:323) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Unknown Source)

 
Can anybody help me to fix this problem w/o performing OS restore? Thanks.

I upgraded fine on a HP ESXi 4.0 server. I didn;t have a lot of custom configuration. That seens to be where all the problems come from. Just make sure you read the readme.

This is not a sql corruption issue.

I opened a ticket with support. After going back and fourth, trying to rebuild the alias database, creating it from scratch, etc,  the error continues to occur.

I'm told that it's an issue with the application itself, and not the aliases DB.

If you try to add aliases with multiple email recipents under more than one alias, you will get the "The application encountered an error" message.

Example:
alias@abc.com joe@abc.com john@abc.com
(all is ok so far)
alias1@abc.com tom@abc.com nancy@abc.com
(still good)
alias2@abc.com john@abc.com
(now you will see the error because john@abc.com appears in alias@abc.com)

Symantec is aware of it, but according to the tech engineer, they have no intentions on fixing the issue right now. Note that this all started after upgrading to version 9. This comes after plunking down over a grand to update premium content, and right on the heels of the Symantic Antivirus Corporate v8 virus definition issues.

Not happy.

Symantec... email me if you want a ticket number or speak with Nathaniel Martin-Long.

My workaround was to create a text file and import it. You'll still get an error, but after uploading it to your appliance, hit the back button on your browser. You'll see "the file imported successfully", and your aliases will work, however, you can not maintain them via the interface. PITA.

I don't know why you think we will not be fixing it anytime soon. The documentation (written 2 weeks ago) from our backline (Level 3 support) engineer team says this will be addressed in the next release (9.0.2).

Title: 'The Protocols->Aliases page shows "Application Error" after upgrade to v9.0.x or addition of a new alias'
Document ID: 2010052713072154
> Web URL: http://service1.symantec.com/SUPPORT/ent-gate.nsf/...

Granted this is not MySQL corruption, but the current fix is to remove the duplicate entries from the MySQL table manually. Please contact support if you aren't able to restore from a recent backup to fix this.

JDavis-

I can not remove the duplicate entries. They are not actually duplicates. I have aliases that need to go to to multiple recipients. I do not have the same email appearing twice in one alias, if that is what you mean.

I'm in the service industry. One alias is an email address that our clients use to refer work to us. Another alias is for them to report payments to us. I need to be in both alias entries, but v9 does not allow this.

The reason I mentioned that the issue was not being fixed anytime soon is because prior to the posting of document ID 2010052713072154, I was told by your support rep that there are no current plans to fix it anytime soon, and that it would "possibly" be in the next release. He acutally suggested that I post my issues here. Today was the first chance I had to do so.

However I am glad to hear that the issue will be addressed. Thank you for the update.

@bokfon

Make sure that there's no activity before performing the upgrade. configure the sbg for "Do not accept message" then reduce/delete spam quarantine message atleast 7 days older, reduce/delete logs message atleast 3 days older. flush all messages left in the message queues and perform the upgrade.
I followed this instruction and succesfully upgrade the sbg 8.0 to 9.0 with no problem...

I Successfuly upgrade 8.0.3 to 9.0 I dont encountered any problems.

Now that this is a 9.01 and a 9.02, we should be clear about which we are upgrading to.

I upgraded from 9.01 to 9.0.2 and am now getting  MTA crashed on Sig 11, and Sig 6