So this is IT more than programming but Google found nothing, and you guys are just the right kind of geniuses.
My Exchange Server 2007 and Entourage clients don't play nice.
Right now the big issue is that the entourage client will not connect to Exchange 2007 ( Entourage 2004 or 2008)
The account settings are correct and use the proper format of https://exchange2007.mydomain.com/exchange/user#domain.com
The issue is with a dll called davex.dll when it is where it belongs, the OWA application pool crashes a whole bunch of nasty things happen.
When it isn’t there, I can connect to everything fine - and the OWA app pool doesn’t crash - but Entourage never propogates the folders in the mailbox and doesn't send or receive.
Any help or ideas would be appreciated: Microsoft support is silent on the issue, and Google doesn't turn up much.
Try it without using the /exchange in the server properties field. Here's a link with relevant info.
davex.dll is the legacy webdav component for Exchange server, which Entourage uses. Your first step should be investigating why the application pool crashes. My guess is that Entourage can't do anything when the dll isn't present because webdav is not responding to any requests.
Related
I know I should probably ask MS about this, but I dont know if I trust their communication tools to get me a satisfying answer.
I have recently taken the task to test an application of mine.
Part of this test is to send an e-mail to it, then log in and see if I get the result I want (this is automated)
For this the process is:
Open Outlook -> Send Mail
Close Outlook
Open App -> Check result
Open Outlook -> Send Mail
Close Outlook
But for some reason, every second time the outlook app is opened, (including manually opening the app to check on configurations etc.) Mails will go to the outbox but will not be sent, unless I manually trigger them to.
Now, there are possible solutions like keeping the app running continously, or telling my testing-suite to press F9 after every sent mail, but I want to tackle the root cause, and fix the underlying problem.
The Outlook Version used is the latest Version of Office 365 Outlook.
Has anyone else had this experience and figured out a fix?
Thank you in advance.
Keep in mind that message submission is an asynchronous process, so if you close Outlook while it is still sending, the message might end up stuck in the Outbox.
You can call Namespace.SendAndReceive to force submission, but it is still asynchronous. You can hook into the SyncObject.SyncEnd event on the first (All Accounts) SyncObject from the Namespace.SyncObjects collection and quite only after that event fires.
Since this problem occured on a machine I do not own, I tried avoiding certain easy troubleshooting steps. After I couldnt find an answer on my own, and I didnt get responses here that would've helped me solve this without a wooden hammer method, I asked for permission to issue a repair to the local office 365 suite.
After the repair it had redownloaded and installed the entirety of office 365.
After connecting my company MS account to outlook, the issue no longer appeared.
I guess this counts as solving this issue.
We have a program written in Delphi that can send emails via simple MAPI
for the people that use MAPI with outlook installed 95% of the time it works fine
but for the 5% of people that it doesn't just work for is there anyway to Test MAPIlooking for something where we can find if there is an issue with our program or if its something that their hardware guy needs to fix.Would be good if its some Microsoft tool or something official so if we go to the clients hardware/IT guy and say test this he will trust the results of the test
some errors we have come across include
api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.
Access violation only for one contact in the outlook address book - happened when calling the MAPIResolveName (no solution found for this - client didnt want to reinstall outlook)
Mapi error 26 for Office build version 1703 - first email goes through ok but they all fail after that. (You can make a work around by using the MapiLogOn and pass the session handle through in the MAPISendMail call)
Either there is no default mail client or the current mail client cannot fulfill the messaging request
I am trying to access a CalDAV account in iCal and everything works fine except for the Delegation tab. I can see the account(s) I have access to (including the correct read/write properties), but the checkboxes are disabled and the calendars cannot be selected. Has anyone seen this before & know what the cause is?
This is a custom CalDAV implementation, so it is likely due to a disconnect between what iCal expects and what our server is sending -- but there are no error/warning messages in the console to indicate what the problem might be.
Any advice would be appreciated.
iCal queries the permissions and methods available on the server. To query the permissions on a collection resource you will need to have the DAV::read-current-user-privilege-set permission. Assuming iCal can read the permissions it will be looking for the DAV::read permission for reading and the DAV::bind, DAV::unbind and DAV::write permissions to indicate the ability to write.
The best way to debug this is probably to read RFC3744 about half a dozen times, interspersed with using iCal against a working server and sniffing the TCP communication as it does it. A good way is to use some kind of man-in-the-middle proxy so you can sniff the communication with (e.g.) Mobile Me or iCloud.
In my limited experience, this happens when the account used for sharing is functional (not personal) in Microsoft Exchange Server 2010. An example, where two of three are functional:
I do use various CalDAV implementations but have never encountered the same limitation, so this may be not a good answer. Also Exchange Web Services (EWS) for calendaring and delegation are probably not comparable to CalDAV. Still, it's food for thought.
The Debug menu of iCal 5.x offers CalDAV logging options.
To enable that menu, you could use the Secrets preference pane.
I have an ASP MVC 2 application, through which I occasionally send emails using SmtpClient.Send(). Typically, emails are sent out in batches of between 1 and 50 emails, with hours or even days passing between batches. I have this all set up so that the emails are actually sending just fine. But, the problem is that when the emails are sent, my site suddenly becomes unavailable for about 15 minutes, and I have no idea why.
My site is hosted on a shared, Windows 2008 server with a third-party web host.
Here is the relevant section in my web.config file, edited for privacy:
<system.net>
<mailSettings>
<smtp deliveryMethod="Network" from="fromemail#doman.com">
<network host="mail.DOMAIN.COM" userName="username" password="password"/>
</smtp>
</mailSettings>
</system.net>
Does anyone have any thoughts or ideas as to why this might be happening? I've been trying to reaserch it and Google it for some time now, but I'm just not coming up with anything.
This really could be many different things but..
The first thing I suggest you do is enable ASP.NET Health Monitoring on your site. This should hopefully help you gain visibility of the exception that is causing this issue (A guide to using Health Monitoring).
For obvious reasons be sure not to choose the Mail Provider to send you your exceptions - perhaps use the SQL provider or write a custom provider that writes to a file.
I would also ask your hosts to look into the Event Log for any information that may be of value.
Hope that helps.
E-mail can be an expensive operation. Have you considered using the asynchronous e-mail send so that the process does not block your main thread?
I'm working on installing vPopMail on CentOS for use with a Qmail / Courier-IMAP mail-server setup. So far, everything is working out well enough. Mail sent to any virtual user I have setup under any virtual domain (assuming MX records are pointed correctly in the domain DNS) I add to vPopMail is routed correctly to the vPopMail ./Maildir/ and is viewable in /home/vpopmail/domains/domain-example.com/user.name/Maildir/new.
The problem I'm having now is telling the pop service to authenticate using vPopMail instead of the ~default~ Qmail / Courier-IMAP authentication method(s).
"You also need to modify your pop server startup line to use the vchkpw program for authentication." (found at http://www.inter7.com/vpopmail/vpopmail.html) is all I can find in any documentation to even give me the clue that that needs to be done.
So, the question:
How do I tell my pop server to authenticate with vPopMail?
Thanks so much in advance! :)
(Feel free to let me know what (if) more info is needed to answer my question..)
Id go ahead and check this out
http://www.inter7.com/vpopmail/install.txt
namely item 12
then go ahead and add those lines to your rc.local file or rc.sysinit
good luck