Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 505
  • Last Modified:

Emailing from within Ms Access

Not sure if this is the best place to post this but here goes.

I have an SBS2003 server (without Exchange) which has an MS Access application running on it. This application needs to send emails once a week to a few people. I used to have Outlook installed on this server, but mindfull of the pitfalls of running Outlook on an SBS Server, I uninstalled it with the intention that my application can use Outlook Express instead.

When my Access application attempts to send it's emails, I now get a runtime error: 2046 - The Command or Action SendObject isn't available now.

I have used Outlook Express in this manner succesfully on another 2003 server. So presumably I need to tweak something in the registry to make it work here.

Anybody got any ideas?
0
ipendlebury
Asked:
ipendlebury
  • 8
  • 8
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Interesting... the pitfalls of running Outlook on an SBS are because of the Exchange Server.  (http://support.microsoft.com/kb/266418) If you don't have that installed then there aren't any problems... other than the fact that you lose ALL that functionality of having an Exchange server!


However, since Outlook Express is not a MAPI client, it won't handle your Access SendObject command.  You need to have a MAPI client on the machine running this.  So, your intention to have OE do the job isn't gonna work.

Jeff
TechSoEasy
0
 
ipendleburyAuthor Commented:
Jeff,

Like I said in my original post, I have another 2003 Server doing the same thing, and Access works fine sending messages through Outlook Express.

So is it possible that the SendObject command isn't using Mapi?

There is no incoming mail to these sites, so running Exchange would be pointless.

Ian
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'm guessing that there is another MAPI client on the other Server 2003.  Is SQL installed on that machine?  Because SQL Mail would work as well.  

SendObject uses MAPI, and as far as I know, that's the only way it works.

Running Exchange wouldn't be pointless if they use mail internally or if they need shared calendaring.  Or... if the Access routine you are trying to run needs a MAPI server!

Jeff
TechSoEasy
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ipendleburyAuthor Commented:
Jeff,

I know that OE is handling these mails on the other server, because they end up in the Sent Items Folder in OE afterwards.

SQL Server isn't installed on the server that doesn't have a problem, but it is installed on the Server that does have the problem.

So perhaps there is another way to make the SendObject action work. How can I tell access to emails via the SQL Server Mapi Server?

I would prefer to know how OE can be made to work like it is on the other server though.

Ian
0
 
ipendleburyAuthor Commented:
Jeff,

I think I should mention also that the server with the problem has been reinstalled a few months ago because of other problems I had. Before the rebuild it worked fine emailing through OE.

Ian
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
0
 
ipendleburyAuthor Commented:
Jeff,

That gave me quite a few things to look at. In particular, there was no [Mail] section in the win.ini file on the problem machine, whereas the 'good' machine did have this section. So I've put a [Mail] section in there, but it didn't make a difference.

I did a search around and found an article which stated that the wrong Mapi32.dll might be left behind after uninstalling Outlook. I checked and found it was totally different from the one on the good machine. I copied it over from the good machine, but it still didn't make any difference.

I get the impression though, that it's not an exact science and that problems are frequent when Mapi mail is sent via OE.

Ian
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Did you reregister the Mapi32.dll after copying it over?

regsvr32 /u "C:\Windows\System32\Mapi32.dll"
regsvr32 "C:\Windows\System32\Mapi32.dll"

Jeff
TechSoEasy
0
 
ipendleburyAuthor Commented:
Jeff,

When I typed the first of those lines, I got the message:

C:\windows\system32\mapi32.dll was loaded but the DllUnregisterServer entry point was not found. This file can not be registered.

I figured that this was because the Mapi32.DLL that was registered was different to the one on the disk. So I put the old one back and tried to unregister that, but I got the same message. So it sounds to me like The old one is also different to what is registered in the system.

Should I reinstall something?

Ian
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Actually getting an error on the first one is okay... as long as you don't get one on the second command.

Jeff
TechSoEasy
0
 
ipendleburyAuthor Commented:
Jeff,

When I try to register the new file I get a similar error:

C:\windows\system32\mapi32.dll was loaded but the DllRegisterServer entry point was not found. This file can not be registered.

Ian
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I was just reminded, as I was answering another question... you can't install SBS Service Pack 1 if Exchange isn't installed.  So, my suggestion?  Install Exchange and move on.

Jeff
TechSoEasy
0
 
ipendleburyAuthor Commented:
Hello Jeff,

Ah this is making more sense now...

I'd forgotten all about this, but when I rebuilt hte server I did install Exchange, but I disabled it.   All this time since, i've had myself convinced that Exchange wasn't installed. SBS sp1 is installed.

If I used Exchange, would I then not have to use Outlook as the client? We've already had the discussion about the wisdom of doing this within the same box. No other pc on the network runs any sort of mail or messaging application, so Exchange would be overkill anyway.

However, this has given me a clue as to what my problem is....

I tried running Exchange System Manager. It bombed out complaining that the Mapi32.dll was the wrong version. I'd thought that old version had belonged to Outllook, but it was obviously installed by exchange. So it hardly seems suprising that Mapi is not working when I've got the Mapi Mail server disabled.

So would it be likely that I would fix anything by uninstalling Exchange?

Am I right in assuming that OE can't talk to Exchange?

Any other comments would be gratefully appreciated.

Ian
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'd just reinstall Exchange at this point, then reapply Exchange SP1.  This will fix the MAPI issue and then you can disable the Exchange Store service.

See http://support.microsoft.com/kb/320202 for the "how-to".

Jeff
TechSoEasy
0
 
ipendleburyAuthor Commented:
Jeff,

I just realised that this question was still open. Yes the solution will be to reinstall Exchange. I just can't get around there at the moment to do it. So i'll award the points in order to close this question.

Thanks for your help.

Ian
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Ok... no prob.  :-)

Jeff
TechSoEasy
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 8
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now