Outlook 2007 "Connection Status..." shows 3 "Disconnected" entries of type "Directory"

Status
Not open for further replies.
M

mrbelk

I have been really fighting some issues with my Exchange2007 server and Outlook2007 clients. I recently installed EX2007Sp1 (rollup 9 installed this morning) hoping to solve these issues. We only have one exchange server with the Client Access, Hub Transport, and MailBox roles installed.

What I am seeing is that Outlook 2007 users cannot see Free/Busy info, cannot accept meeting requests, cannot see the global address list, cannot turn on the out of office assistant, etc. All of these things work within OWA, however. I get an error dialog to the effect that the connection to exchange is unavailable. I can send/receive email just fine

What I see when I CTRL+Click on the Outlook tray icon shows several entries for " Directory" that have a status of " Disconnected." The server name for all those entries is the NETBIOS name of my exchange 2007 server, whereas the entries for " Public Folders" and " Mail" all point to the FQDN of the exchange server.

When I do a test of the Autoconfiguration stuff, it appears to come back successfully.

Any suggestions would be most appreciated.

-Matthew Belk
 
H

Harpreet Singh Khandiyal

Hi Matthew,

If the " Directory" option is showing as disconnected, it could either mean that there is some issue with DC or with the DSProxy component which is not able to contact the DC.

Try to do a nslookup from the client for the Exchange Server's netbios name and FQDN. Check if you get correct IP address.

Let me know while configuring Outloook is your name getting identified against the exchange server?

Before trying the auto discover part, try to manually configure the Outlook Profile and check if thats working or not.

You can click on " Test Email Auto Configuration" option next to the Connection Status option when you do a Ctrl+Click.

Also check if the System Attendant Service is running on the Exchange Server?Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375)
 
M

mrbelk

Harpreet,

NSLookup is fine, the Netbios and FQDN resolve correctly.

If I delete my existing Exchange account info and add a new Mail profile and a new Exchange account, if I use the exchange server FQDN or NETBIOS, the wizard comes back as the exchange server isn't available. However, if I use the DC name and click the " Check Name" button, the exchange server is filled in correctly, and my user name is found.

The " Test email configuration" returns no errors.

the System Attendant service is running.

I hope that sheds some light...

Thanks,

Matthew
 
H

Harpreet Singh Khandiyal

We have an issue over here. The check name should always work with the Exchange Server name and getting the check name done with the GC name is a troubleshooting step.

Please install the following hot fix on the Outlook client and let me know if the check name works with Exchange Server name or not.

Description of the update for Outlook 2007: June 9, 2009

http://support.microsoft.com/kb/969907

If the issue still persists, then please try out the steps as per the below mentioned article

Error message when you create a profile in Outlook 2007 after you install the cumulative update that is described in Microsoft Knowledge Base article 961752: " Outlook cannot log on"

http://support.microsoft.com/Default.aspx?kbid=969519

Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375)
 
M

mrbelk

That Outlook 2007 update was already installed.

I ran through the steps in the linked KB article. Symptom 1 most closely approximates my situation, and I tried resolution methods 1 and 2. Method 1 doesn't work; I just get a message that Outlook cannot connect to the exchange server. I implemented Method 2 (I didn't have any DWORD values for the " No RFR Service," so I added one). That resolution didn't work, either.

Any other suggestions?

-Matthew
 
M

Mike Shen

Hi Matthew,

I think that we need to solve "Directory" disconnected issue firstly. At this time, would you please let me know?

1. Whether all the Outlook Clients encounter the problem?

2. How the Outlook connects to Exchange Server (RPC or RPC over Http)?

3. I suggest you increase MSExchangeSA\NSPI Proxy and MSExchangeSA\RFR Interface to expert:

Set-eventloglevel "MSExchangeSA\NSPI Proxy" "level expert

Set-eventloglevel "MSExchangeSA\RFR Interface" "level expert

Then, please reproduce the issue and check whether any error event can be located in Application log

I would like to explain when creating Outlook Profile, the Outlook Client needs to contact the Exchange Referral component which will redirect the Outlook client to a GC server. From your description, if we fail to create Outlook Profile when typing Exchange Server name and able to create Outlook Profile by using GC server name, the issue mostly occurs because the Outlook fail to contact the Exchange Referral component.

Therefore, please also let me know whether the Outlook connects to Exchange Server directly or through any network device or firewall. In addition, please run rpddump on the Exchange server to check related ports have been listened by Exchange Server:

RPCdump /s <exchange mailbox server>

You should get information like below:

If Outlook connects to Exchange through RPC over TCP:

ncacn_ip_tcp(Connection-oriented TCP/IP)

192.168.1.2[1394] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED

192.168.1.2[1416] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED

If Outlook connects to Exchange through RPC over HTTP:

ncacn_http(Connection-oriented TCP/IP using Microsoft Internet Information Server as HTTP proxy.)

192.168.1.2[6002] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED

192.168.1.2[6004] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED

Mike Shen


 
V

--Vinod--

Hi,
Have you installed this EX2007 on DC? or is it a Member server? I would try restarting the AD Topology service.
 
M

mrbelk

Hi Matthew,

I think that we need to solve "Directory" disconnected issue firstly. At this time, would you please let me know?

1. Whether all the Outlook Clients encounter the problem?

2. How the Outlook connects to Exchange Server (RPC or RPC over Http)?

3. I suggest you increase MSExchangeSA\NSPI Proxy and MSExchangeSA\RFR Interface to expert:

Set-eventloglevel "MSExchangeSA\NSPI Proxy" "level expert

Set-eventloglevel "MSExchangeSA\RFR Interface" "level expert

Then, please reproduce the issue and check whether any error event can be located in Application log

I would like to explain when creating Outlook Profile, the Outlook Client needs to contact the Exchange Referral component which will redirect the Outlook client to a GC server. From your description, if we fail to create Outlook Profile when typing Exchange Server name and able to create Outlook Profile by using GC server name, the issue mostly occurs because the Outlook fail to contact the Exchange Referral component.

Therefore, please also let me know whether the Outlook connects to Exchange Server directly or through any network device or firewall. In addition, please run rpddump on the Exchange server to check related ports have been listened by Exchange Server:

RPCdump /s <exchange mailbox server>

You should get information like below:

If Outlook connects to Exchange through RPC over TCP:

ncacn_ip_tcp(Connection-oriented TCP/IP)

192.168.1.2[1394] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED

192.168.1.2[1416] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED

If Outlook connects to Exchange through RPC over HTTP:

ncacn_http(Connection-oriented TCP/IP using Microsoft Internet Information Server as HTTP proxy.)

192.168.1.2[6002] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED

192.168.1.2[6004] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED

Mike Shen



Thanks for this post, Mike.

Some answers to your questions:

All Outlook clients exhibit this behavior

we connect via RPC over TCPIP (we do not use Outlook Anywhere, we use OWA to connect outside the office)

we do not connect through any intermediaries like firewalls or proxy servers; all clients are on the local network

The output of rpcdump looks like this (for the ncacn_tcp_ip section)

ncacn_ip_tcp(Connection-oriented TCP/IP)
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1025] [906b0ce0-c70b-1067-b317-00dd010662da] :NOT_PINGED
10.0.254.19[1037] [12345678-1234-abcd-ef00-0123456789ab] IPSec Policy agent endpoint :NOT_PINGED
10.0.254.19[1037] [12345778-1234-abcd-ef00-0123456789ac] :NOT_PINGED
10.0.254.19[1059] [b9fadb8d-53a1-41d7-b763-88d884b6b829] Microsoft Exchange Topology Information Server RPC Interface :NOT_PINGED
10.0.254.19[1065] [5261574a-4572-206e-b268-6b199213b4e4] Exchange Server STORE Async EMSMDB Interface :NOT_PINGED
10.0.254.19[1065] [a4f1db00-ca47-1067-b31f-00dd010662da] Exchange Server STORE EMSMDB Interface :NOT_PINGED
10.0.254.19[1065] [a9e05b20-6f57-4e24-a540-52412017e6ff] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [bf6dd426-77b4-44b3-984e-d413fc075562] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [1453c42c-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [10f24e8e-0fa6-11d2-a910-00c04f990f3b] Microsoft Information Store :NOT_PINGED
10.0.254.19[1065] [da107c01-2b50-44d7-9d5f-bfd4fd8e95ed] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [99e64010-b032-11d0-97a4-00c04fd6551d] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [89742ace-a9ed-11cf-9c0c-08002be7ae86] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1065] [a4f1db00-ca47-1067-b31e-00dd010662da] Exchange Server STORE ADMIN Interface :NOT_PINGED
10.0.254.19[1108] [f1f21151-7185-4170-ac8d-9bb077c29bd3] :NOT_PINGED
10.0.254.19[1116] [76c0d124-a18e-49d4-adf1-d8c6ba868ea6] :NOT_PINGED
10.0.254.19[1135] [37fc1b02-da36-4b27-a745-bf2f58a98ff6] :NOT_PINGED
10.0.254.19[1140] [52d3f3f5-248c-4d74-a01f-a06e41d5cd59] :NOT_PINGED
10.0.254.19[1160] [41f5fae1-e0ac-414c-a721-0d287466cb23] :NOT_PINGED
10.0.254.19[1160] [bd5790c9-d855-42b0-990f-3dfed8c184b3] :NOT_PINGED
10.0.254.19[1160] [8384fc47-956a-4d1e-ab2a-1205014f96ec] :NOT_PINGED
10.0.254.19[12634] [1544f5e0-613c-11d1-93df-00c04fd7bd09] MS Exchange Directory RFR Interface :NOT_PINGED
10.0.254.19[12656] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS Exchange Directory NSPI Proxy :NOT_PINGED
10.0.254.19[12634] [3cb4be69-9ba1-448c-9a44-a1f759a1878a] MS Exchange Recipient Update Service RPC Interface :NOT_PINGED
10.0.254.19[12634] [f930c514-1215-11d3-99a5-00a0c9b61b04] MS Exchange System Attendant Cluster Interface :NOT_PINGED
10.0.254.19[12634] [83d72bf0-0d89-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Private Interface :NOT_PINGED
10.0.254.19[12634] [469d6ec0-0d87-11ce-b13f-00aa003bac6c] MS Exchange System Attendant Public Interface :NOT_PINGED

after setting the log level for the MSExchangeSA service, I see several log entries like this:

Event Type: Information

Event Source: MSExchangeSA

Event Category: RFR Interface

Event ID: 9073

Date: 8/4/2009

Time: 9:12:05 AM

User: N/A

Computer: BIZSVSERVER01

Description:

The Directory Service Referral interface (RFRI) received a client request on RPC protocol sequence ncacn_ip_tcp. RFRI is returning the Domain Controller name bizsvserver01.bizspeed.com.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

****************************

It should be noted that the server in this preceding log event (bizsvserver01.bizspeed.com) is our exchange server, not our domain controller.

****************************

and some log errors like this:

Event Type: Error

Event Source: MSExchangeSA

Event Category: RFR Interface

Event ID: 9143

Date: 8/4/2009

Time: 9:10:04 AM

User: N/A

Computer: BIZSVSERVER01

Description:

Referral Interface cannot contact any Global Catalog that supports the NSPI Service. Clients making RFR requests will fail to connect until a Global Catalog becomes available again. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and this:

Event Type: Error

Event Source: MSExchangeSA

Event Category: NSPI Proxy

Event ID: 9057

Date: 8/4/2009

Time: 9:10:04 AM

User: N/A

Computer: BIZSVSERVER01

Description:

NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service. New clients will be refused until a Global Catalog is available. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and some errors like this:

Event Type: Error

Event Source: MSExchangeSA

Event Category: NSPI Proxy

Event ID: 9176

Date: 8/4/2009

Time: 9:05:04 AM

User: N/A

Computer: BIZSVSERVER01

Description:

NSPI Proxy can contact Global Catalog bzspdatldc02.bizspeed.com but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients. Reboot bzspdatldc02.bizspeed.com as soon as possible.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

We only have one domain controller in the organization, and I'm pretty sure it's the global catalog server.

Thanks,

Matthew
 
V

--Vinod--

" We only have one domain controller in the organization, and I'm pretty sure it's the global catalog server." is the exchange installed on this box?
 
M

mrbelk

" We only have one domain controller in the organization, and I'm pretty sure it's the global catalog server." is the exchange installed on this box?


No. Exchange is on a member server. I was not aware that installing Exchange 2007 on a domain controller was a supported configuration.
 
M

mrbelk

Check out this article

http://support.microsoft.com/kb/279742

Also run Microsoft Exchange Best Practices Analyzer, see if there are any errors

Run a DcDiag using the following syntax from the exchange server and check if there are any connectivity issues

DcDiag /v /s:<DC's NetBios Name> Harpreet Singh Khandiyal (http://support.microsoft.com/kb/555375)

Which BPA scan should I run?

running the dcdiag command on the exchange server showed no errors.

W.R.T. the KB article you referenced, my DC is not multihomed, so that article doesn't apply to me. I did ensure that the only network adapter in the system is bound to File and Printer sharing. the application event log on the exchange server still reports that it thinks the domain controller is itself.

If I promote my exchange server to a DC, will that correct my problems? Is that a supported configuration?

Thanks,

Matthew
 
M

Mike Shen

Hi Matthew,

1. I would like to know if you configure the an Outlook Client to use specific Global Catalog server (bzspdatldc02.bizspeed.com), whether the Directory connection issue could be solved. You can refer to following article:

Note: Please let me know whether "bzspdatldc02.bizspeed.com" indicated in event 9176 is the only GC server in the organization. Please also ensure the Outlook is able to resolve bzspdatldc02.bizspeed.com to correct IP address.

How to configure Outlook to a specific global catalog server or to the closest global catalog server

http://support.microsoft.com/kb/319206/en-us

2. If Directory connection issue could be solved after specify the GC server, I suggest you check the 2080 event on the Exchange Server:

Event ID 2080 from MSExchangeDSAccess

http://support.microsoft.com/kb/316300/en-us

Please ensure the GC server can be detected by Exchange Server.

Regarding your question, I would like to explain that Microsoft does not recommend to install Exchange Server on GC.

Mike
 
M

mrbelk

Hi Matthew,

1. I would like to know if you configure the an Outlook Client to use specific Global Catalog server (bzspdatldc02.bizspeed.com), whether the Directory connection issue could be solved. You can refer to following article:

Note: Please let me know whether "bzspdatldc02.bizspeed.com" indicated in event 9176 is the only GC server in the organization. Please also ensure the Outlook is able to resolve bzspdatldc02.bizspeed.com to correct IP address.

How to configure Outlook to a specific global catalog server or to the closest global catalog server

http://support.microsoft.com/kb/319206/en-us

2. If Directory connection issue could be solved after specify the GC server, I suggest you check the 2080 event on the Exchange Server:

Event ID 2080 from MSExchangeDSAccess

http://support.microsoft.com/kb/316300/en-us

Please ensure the GC server can be detected by Exchange Server.

Regarding your question, I would like to explain that Microsoft does not recommend to install Exchange Server on GC.

Mike

Mike,

I tried explicitly setting the GC server and I no longer see the " disconnected" messages in the connection status window and the global address list, out of office assistant, and the scheduling assistant comes up. I also tried setting the " Closest GC" value and that setting seems to have resolved the problem as well.

So, what could have changed to now require this registry value? I don't mind adding that particular registry key on all of my workstations, but I am curious as to why I now require this entry when before I didn't.

Thanks,

Matthew
 
M

Mike Shen

Hi Matthew,

Firstly, I would like to explain how the Outlook connects to Directory Service normally:

1. The Outlook connects to Exchange Referral service

2. The Exchange Referral service refer the Outlook to a GC Server

3. The Outlook connects to the GC NSPI Service

In your case, from the event log, we can see the Exchange Server is not able to contact the NSPI service on the GC server. The issue may occur if the NSPI service does not work on GC server or Exchange fail to connect to the NSPI service.

As the Outlook is able to connect to GC after configuring the registry key, I think the issue may occur because the Exchange Server is not able to connect NSPI service.

Therefore, I suggest you post the 2080 event here on the Exchange server to check whether the Exchange Server is able to detect the GC server.

In addition, please run rpcdump tool on the GC server, under ncacn_ip_tcp, you should get entry like below:

192.168.1.1[1025] [f5cc5a18-4264-101a-8c59-08002b2f8426] MS NT Directory NSP Interface :NOT_PINGED

Then, please run Rpcping on the Exchange server to ping the GC sever, please check whether any error is encountered.

Rpcping "t ncacn_ip_tcp "s bzspdatldc02.bizspeed.com "e 1025 (based on your rpcdump result)

Note: I assume that bzspdatldc02.bizspeed.com is your GC server.

Thanks

Mike
 
N

Nepharious

I am having this same issue. Also like Mr Belk, adding the registry entry per article 319206 fixes the problem for the machine that I do the registry entry on. Unlike Mr Belk, this is not a solution for me as I have 1000+ users that I can not be adding this registry entry to in order to fix the problem.

This is a result of migrating Exchange from 2003 server to 2007. I have two servers...

1. Front End / Domain Controller / Windows 2008 64 bit / Exchange 2007

2. Back End / Windows 2008 64 bit / Exchange 2007

How do I determine that " Exchange Server is not able to connect NSPI service" and determine that " Exchange Server is able to detect the GC server" ?

Thanks!
 
N

Nepharious

I was able to resolve this on the server by making a DNS change and disabling IPv6 on the nic cards.

The primary fix for this is DNS. My issue was resolved when I found that a record in DNS for _msdcs had an NS record pointing to my old 2003 server that had been shut down. I did some research and found that _msdcs is directly related to the Global Catalog Server. This explains why clients could not connect to the GCS to print emails, find users in the Global Address List, and add calendar items and such.

After adjusting the NS record under " _msdcs" to point to my new front end server, the problem was solved. One additional thing I did on the server was disable IPv6 on both the front and back end servers. I think this also helped the issue but was able to verify that the DNS record change was ultimately the fix.

To help clean up the DNS, I went though and looked at all the DNS records and made sure that anything pointing to my old servers was removed. Just be sure and not remove the _msdcs one. Adjust it to the new server and the issue should be resolved.
 

dizzycop4856

Member
Outlook version
Outlook 2007
Email Account
POP3
fleshlight y9765

10.07.2012 · Super Hot South Indian film actress Meena Hot Nude,Naked FAKE photo - Meena topless without bra, and a lucky guy pressing her boobs hard and sucking them! fleshlight The sexy American actress Courteney Cox nude showing off her amazing pussy and ass. A very hot Courteney Cox fake nude photo. .
 
Status
Not open for further replies.
Similar threads
Thread starter Title Forum Replies Date
M connection to the microsoft exchange server has been lost. outlook 2007 Exchange Server Administration 0
S Outlook 2007 crash linked to gdiplus.dll Using Outlook 0
S Outlook 2007 - Automatic purge fail Using Outlook 0
J outlook 2007 doesn't let me choose which .pst to search Using Outlook 2
D Outlook 2007 vs. Outlook 2010 -- ToDo Bar Using Outlook 0
D Outlook 2007 on 365 Using Outlook.com accounts in Outlook 2
S Macro for other actions - Outlook 2007 Outlook VBA and Custom Forms 23
S Verwendung von Outlook 2007 Using Outlook 0
A Arthur needs help with 2007 Outlook e-mail Using Outlook.com accounts in Outlook 3
M PST import from Outlook 2007 to 2010 - Address Book contacts all in 1 group Using Outlook 4
S outlook 2007 calendar search Using Outlook 6
B Migrate Outlook 2007 to Office 365 Using Outlook 3
X I have met my waterloo trying to resolve embedded graphics problem with outlook 2007 and now 2016 Using Outlook 1
R Outlook 2007 only loads some appointments Using Outlook 0
C Move Outlook 2007 to new PC with Outlook 365 Using Outlook 3
J Outlook 2007 Hide Messages Option not Available Using Outlook 2
S Outlook 2007 Calendar instant search problem. Windows 7 Using Outlook 4
S Outlook 2007 Calendar instant search problem. Windows 7 Using Outlook 0
B Server errors Outlook 2007 Using Outlook 1
S Reboot of frozen windows7 results in changed outlook 2007 settings Using Outlook 1
S Outlook 2007 printing wrong email address at top of page Using Outlook 8
M Configure outlook 2007 to accept digital signatures Using Outlook 2
D Outlook 2007 crashes when opening an email Using Outlook 2
R New chap saying hello and needing advice on Outlook 2007 thumbnails Using Outlook 3
icacream From Outlook 2007 to 2016 ! Using Outlook 9
vodkasoda Object could not be found Error in Outlook 2007 Outlook VBA and Custom Forms 5
S Outlook 2007: Address Cards allow entering text! Why? Using Outlook 3
S View Appointment in Text Wrap in Outlook 2007 Month Calendar View Using Outlook 0
L Outlook 2007 Separate the Send/Receive functions Using Outlook 2
M Outlook 2007 Contacts Glitch: Creating a new email Using Outlook 1
C Move from Outlook 2007 Enterprise (MOE) to Outlook Pro plus 2007 Using Outlook 1
J reinstalling Outlook 2007 asking for user name & password Using Outlook 14
P outlook addin unloaded in office 2007 Using Outlook 0
B Fonts in Outlook 2007 Using Outlook 4
R Add Exchange Account to existing POP3 Outlook 2007 Profile Using Outlook 0
C out of space in file group Outlook 2007 Using Outlook 2
A Moving archived contents in Outlook 2007 back into working folders Using Outlook 0
P Outlook 2007 Email Categorization using VBA Outlook VBA and Custom Forms 1
M Unable to Configure Gmail Account in Outlook 2007 Using Outlook 1
R Outlook 2007 or 2010 - Lock Down Functionality Outlook VBA and Custom Forms 3
S Outlook 2007, windows 10 Font size Using Outlook 1
Diane Poremsky Manually create a POP3 account in Outlook 2007 Using Outlook 0
J Can Click to Drag Custom Form Field But Cannot Drop When Designing in Outlook 2007 Outlook VBA and Custom Forms 2
L Outlook 2007 Font Using Outlook 3
J Outlook 2007 connector and Windows 10 Using Outlook 3
R Outlook 2007 - Shared Accounts and Resources without Exchange Server Using Outlook 0
L Outlook 2007 - Macro Re Search Using Outlook 16
D Outlook (Office) 2007 & Windows 10 Pro Using Outlook 6
MattC Problem with Outlook 2007 & iCloud / duplicate tasks Using Outlook 1
D Outlook 2007 e-mail header- How to set font & font size in received message headers ? Using Outlook 2

Similar threads

Top