Upgrading from 4.1.3 to 4.1.5
 

:? I'm fairly new to administering the BES. Just inquiring as to how simple it may be to move from 4.1.3 to 4.1.5. Do I have to move to 4.1.4 before going 4.1.5?

You can go directly to 4.1.5 using the upgrader package.

Service packs are cumulative, so 4.1.5 contains all of the fixes that were in 4.1.4 and 4.1.4 MRs & HFs.

Upgrader package? I was hoping it was a matter of just downloading the software from RIM, popping it into the CD-ROM and running it.

It is that simple.
Since you already have BES 4.1.3, you just need to download Service Pack 5 for BES 4.1

You don't need to download the full version of BES 4.1.5... you just need the service pack to do the upgrade.

Ok great. I'll be doing that. Thanks for the insight. I'll let you know how it turns out.

Just make sure you back up your DB and server for that "just in case"

My Upgrade was flawless but I did make a backup first.
You just never know.

^^ Excellent advice right there.

Did the backup but now when i'm running the installer pack, i get to the point where it wants to upgrade the database. When trying to do so, i receive error message stating "An attempt to upgrade the database was unsuccessful. An error occured while executing an SQL statement."

What does your log say?

C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\setup<TimeAndDateStamp>.log

I recommend removing all the Roles during the upgrade, just in case someone has the BB Manager Console open on their PC

Oy!

1) Restore the database from your backup
2) Make sure the user object connecting to SQL has the 'sysadmin' role within the SQL Server. Having dbo on the BESMgmt database IS NOT SUFFICIENT.
3) Start upgrade again

If it fails again either post the upgrade installation log file or call T-Support ... I'd recommend the latter if BES is critical for you at all ... it'll be the best $ you spend. If you can wait for a response; well then post here.

just want to add...
i'm doing an upgrade from 4.1 to 4.1.6 and got the same error. the problem was that the db log file could not growth. once set to auto growth everything worked.