I'll look into it (but I can't really promise you anything to be honest)
Mike,
I'm pleased to say that the .912 build appears to have resolved the issue. Interestingly, if you run the install which will upgrade the app, the errors persist. Fully uninstalling the app and reinstalling seems to have done the trick.
I have a case open 02035787 and have been told to watch the https://www.veeam.com/kb2217 and requested to close the case. Can you please send me a link for the patch?
Many thanks for the download link. It nearly works...let me explain. All mail boxes now back up but one mail box (Administrator) doesn't have an O365 licence so I receive the following two lines: -
18/01/2017 08:27:28 :: Mailbox Administrator () doesn't have a valid Microsoft Office 365 license
18/01/2017 08:27:28 :: Processing mailbox Administrator@{domain}.{tld} failed with error: Failed to get folder properties. An internal server error occurred. The operation failed., Mailbox 'Administrator ()' doesn't have a valid license.
This in itself isn't a problem as the important stuff is backed up (hooray!) From a personal point of view however, I like to run my eye down the emails in the morning and see all green and Successful. If I see red or amber (Failed/Warning) it means I have to go digging around to investigate.
Pre upgrade this morning and pre failures from the 01/01/2017 the backup job quite happily skipped Administrator. The job is defined as Backup All as opposed to Backup Selected so I don't have to change jobs every time somebody new starts.
Let me know if you need me to test any further, I shall also copy this to the forum post in case others happen across the same issue.
We also get this error (Object reference not set to an instance of an object) from a couple of the mailboxes. I would also like a download link if there is a hotfix for it. PM please!
FWIW - I would like to see a toggle under options to say something like 'Report license warnings, but still treat the job as a success'.
I have my job set to 'all mailboxes' so switching it to remove two or three unlicensed mailboxes is a pain when I have 150 that are licensed. It would also introduce the problem of ongoing maintenance when adding new users and needing to make sure they are added to the job.
Hi All,
As promised. Appeared on the website seconds ago, the long awaited update that fixes the issue, including some other fixes also. Everything can be found in this KB: https://www.veeam.com/kb2224!
For the sake of others, I had some minor issues with the service not starting when I upgraded.
I use a non-domain repository, which entails changing the service's logon account. During the install, the logon credentials were swapped back to the default 'Local System' account. After I changed them back to my custom account, everything worked fine.
I got hold of the hotfix before it was public, and the backups worked fine. However, we do get an error for unlicenced users. From what I understand, Update 1 for Veeam Backup for Office 365 is only going to give a warning.
Are there any differences between the pre-release-hotfix and the public Update 1? I can't install it since the build number is the same (912), so I would presume the hotfix and public update is identical?
Judging by the build number, you have the update that went public already installed.
Any chance you previously tried to process all mailboxes, while now adding mailboxes explicitly? Behavior is a bit different in these cases, due to some internal logic (in the first case the job will give an error for each unlicensed mailbox and finally fail after retry). As a workaround, you can try to assign and revoke licenses from these mailboxes in Office 365 admin center, this should ensure Veeam Backup for Office 365 doesn't touch them.
Actually, it's the other way around. We initially started out backing up a few mailboxes, and increased the number gradually to see how long the backup would take. In the end we switched to 'all mailboxes'
I have the same issue. Set to all mailboxes and first job shows a warning status but shows 42 failures in the job, then 3 retries all have status failed.
Just to avoid further confusion, the unlicensed mailbox issue is a different one, the original 'Object reference not set to an instance of an object' issue started to occur on January, 1st and discussed in this thread is fixed by the Update 1. The behavior you're describing is expected for such mailboxes (not licensed in Office 365).
