It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.
Microsoft Access can not send emails after security updates applied.
I updated to office 2010 on server 2012R2. After running all Microsoft updates, Microsoft Access will no longer send emails.
Error: "Microsoft Access can't send a message for the reason stated in the preceding alert. ... Before attempting to send an e-mail message from Microsoft Office Access, resolve the problem identified in the previous message, or configure your computer to send and receive e-mail messages".
Using the "Email Database Object" to send a query. Ran perfectly for years prior to update.
Please advise.
Error: "Microsoft Access can't send a message for the reason stated in the preceding alert. ... Before attempting to send an e-mail message from Microsoft Office Access, resolve the problem identified in the previous message, or configure your computer to send and receive e-mail messages".
Using the "Email Database Object" to send a query. Ran perfectly for years prior to update.
Please advise.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
There is a recent bug that might be related:
https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec
Make sure you update to the fixed build, try again and let us know if that took care of it, and if not, if there are any other messages.
Jim.
https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec
Make sure you update to the fixed build, try again and let us know if that took care of it, and if not, if there are any other messages.
Jim.
I use a macro and the sendemailobject method.
All seemed perfect until a large batch of windows updates were run.
The server does have outlook loaded on it, so I assume the macro sends via outlook.
All seemed perfect until a large batch of windows updates were run.
The server does have outlook loaded on it, so I assume the macro sends via outlook.
Check if this :https://support.microsoft.com/en-ph/help/263084/how-to-work-with-the-outlook-e-mail-security-update-in-an-access-datab
applies to your case
applies to your case
That's exactly my issue, but it appears that Microsoft stripped off all the links included within that bulletin.
"Sorry, page not found"
"Sorry, page not found"
The other “fix” is to use a 3rd party lib like vbMAPI:
https://www.everythingaccess.com/vbmapi.asp
or Outlook redemption, another 3rd party product.
Both avoid the security dialogs when sending e-mail in code.
Jim
https://www.everythingaccess.com/vbmapi.asp
or Outlook redemption, another 3rd party product.
Both avoid the security dialogs when sending e-mail in code.
Jim
Mark,
I'm guessing that somewhere in your code or macro you are attempting to perform an UPDATE query, but have used SetWarnings False prior to calling that line of code. I found this in one of my clients applications. Syntax looked like:
Docmd.SetWarnings False
Docmd.OpenQuery "QueryName" 'this is an update query
docmd.setWarnings True
Because they had SetWarnings False, the error message associated with the links that Jim and John referenced are hidden from you. Check the macro and see if you have this type of syntax. If so, look at the link that JIm gave you to resolve this problem.
HTH
Dale
I'm guessing that somewhere in your code or macro you are attempting to perform an UPDATE query, but have used SetWarnings False prior to calling that line of code. I found this in one of my clients applications. Syntax looked like:
Docmd.SetWarnings False
Docmd.OpenQuery "QueryName" 'this is an update query
docmd.setWarnings True
Because they had SetWarnings False, the error message associated with the links that Jim and John referenced are hidden from you. Check the macro and see if you have this type of syntax. If so, look at the link that JIm gave you to resolve this problem.
HTH
Dale
Hello team. I appreciate your responses.
i've worked through each of these suggestions, but no success yet.
I'm happy to do a 3rd party app, but I reached out to them with the error and they did not think it was something that would be corrected with their software.
Dale, the macros only send a query (no updates) that give the error - screen shots below.
Some old solutions show that it might be an old (circa 2012) issue from Microsoft but their hot fixes were removed. Seems that "EmailDatabaseObject" may no longer work after applying some old windows updates.
Capture.PNG
Capture1.JPG
i've worked through each of these suggestions, but no success yet.
I'm happy to do a 3rd party app, but I reached out to them with the error and they did not think it was something that would be corrected with their software.
Dale, the macros only send a query (no updates) that give the error - screen shots below.
Some old solutions show that it might be an old (circa 2012) issue from Microsoft but their hot fixes were removed. Seems that "EmailDatabaseObject" may no longer work after applying some old windows updates.
Capture.PNG
Capture1.JPG
I'm happy to do a 3rd party app, but I reached out to them with the error and they did not think it was something that would be corrected with their software.
I'm not sure why not. What changed in Office 2010 is the Outlook security model. Now it's not possible to get around certain things when you work in code (Macro or VBA). vbMAPI is a try before you buy, so you can download it and give it a go.
But with that said, on this:
Ran perfectly for years prior to update.
are you saying it was an Office update for 2010 that caused the problem, or that you just updated to Office 2010 from a prior version?
Jim.
Hi Jim - thanks for the response.
I sent them an email with the error, and they said they were not aware of that error, so they couldn't confirm it would fix it. They explained that their software would require changes to create the attachments as temp files, and then send those attachments within their program. So... that seemed ok, but likely not a fix to my issue.
I had office 2007 on this machine until last week. I upgraded to office 2010, and actually everything was fine even after rebooting. however, overnight, wsus sent down Office 2010 security patches, and that's when it failed. Thought I could just remove the security patches, but no go. Thought I could just roll back to Office 2007, but it actualy continues to apply those patches to Office 2007.
I do have a complete vm snapshot that I'm planning to roll back tonight. It's probably the cleanest solution at this point.
Mark
I sent them an email with the error, and they said they were not aware of that error, so they couldn't confirm it would fix it. They explained that their software would require changes to create the attachments as temp files, and then send those attachments within their program. So... that seemed ok, but likely not a fix to my issue.
I had office 2007 on this machine until last week. I upgraded to office 2010, and actually everything was fine even after rebooting. however, overnight, wsus sent down Office 2010 security patches, and that's when it failed. Thought I could just remove the security patches, but no go. Thought I could just roll back to Office 2007, but it actualy continues to apply those patches to Office 2007.
I do have a complete vm snapshot that I'm planning to roll back tonight. It's probably the cleanest solution at this point.
Mark
Well you don't have many choices here outside of rolling back.
It's either CDO or something like vbMAPI, and both will require changes to the app.
Jim.
It's either CDO or something like vbMAPI, and both will require changes to the app.
Jim.
Mark,
You should be able to roll back those update (uninstall them), and then should be able to configure Office not to install update except with your permission.
but your error message says: "Microsoft Access can't send a message for the reason stated in the preceding alert."
What was the reason stated in the "preceding alert"?
You should be able to roll back those update (uninstall them), and then should be able to configure Office not to install update except with your permission.
but your error message says: "Microsoft Access can't send a message for the reason stated in the preceding alert."
What was the reason stated in the "preceding alert"?
no preceding alert - seems like an ambiguous message - checked the logs and nothing there.
Although the error message has not changed, I'm starting to wonder if my attempts to repair have compounded the issue.
The take way - don't upgrade office so close to retirement !
I just looked at my wsus server was set to "approve installation, but not approve un-installation. I'll change that and try again.
Thanks to all. I'll close and share points.
Although the error message has not changed, I'm starting to wonder if my attempts to repair have compounded the issue.
The take way - don't upgrade office so close to retirement !
I just looked at my wsus server was set to "approve installation, but not approve un-installation. I'll change that and try again.
Thanks to all. I'll close and share points.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial