Your system crashed - does that mean you had to restore from backup? Or did it lose power and you had to bring it back up from that? Please provide more detail on that.
Anyway, If you expand recipients, then All Global Address Lists, do you have a Default Global Address list there? If so, go into the properties of it, and click Preview on that first page and make sure it returns all the recipeients in your organization. Let us know what happens. Marc Creviere
This is the same problem Im seeing at the moment after applying the Hot fixes today - I suspect a permissions problem somewhere but Im not sur ewhere ... My outlook users can enter notes but cannot enter contacts or appointments - Is that the same with you ?
My users can login to the domain fine - It just seems that exchange related services are broken ...
Not sure if it is the same problem Elricho, I don't think mine is a permissions problem to be honest.
Marc, thanks,
The crash was a reboot while people were connected to Outlook. I had been working trying to sort out a firewall problem and reconfiguring and so on. I thought everyone had disconnected from Outlook, but some hadn't and their machines froze.
Now no one can see the GAL. I have looked in Exchange manager and can see the addresses in the preview pane, although at the top, there is half of the properties sheet that is just blank, under "these recipients will be included etc etc". I wish there were some way to post screen shots on here!
Below that, all the individual addresses are listed. But not showing up in Outlook on the clients.
The other thing which is strange now, is the printing problem with e mails; they won't print. The printer dialog box appears, then the error message "no matching entries". I can, however, save the e mails and print them that way, I can also print any attachments
Maybe I was wrong about the permissions, I have checked the permissions for the GAL and the only people with permissions are administrators. There are no permissions present at all for authenticated users, or everyone. I am not sure what the permissions should be. The "allow inherited permissions" check box is checked.
Yes, I did reboot, but still can't see the GAL or print e mail.
Yes, I got the following at around that time.
Category Service Control
Event ID 8250
Source MSExchangeAL
The Win32 AAPI call 'DsGetDCNameW' returned error code (0x862)The specified component could not be found in the configuration information. The service could not be initialised. Make sure that the operating system was installed properly.
Does this sound very ominous? I am really hoping I haven't corrupted Exchange by rebooting whilst people were connected.
When Outlook address book is opened, the names are just not there, there is no error message. The other address lists are e.g. All contacts.
I will try creating another profile tomorrow, I am VNC-ing into the server from home at the moment.
I'm not sure what that error means, nor have I been able to find it in the MS knowledge base or on eventid.net. I wouldn't necessarily say it's very ominous - might have been something trying to run after some services had shut down that it needed. Check through your logs for another error that matches it. Also, check your services to see if there are any services that are set to automatic that have not started. Unfortunately I don't know what else to tell you. Marc Creviere
I will what you suggest and if I can find out what happened will post here. Our biggest problem will be if we cannot print e mails and so on I suppose, but I am hoping the problem will have resolved itself by the time people log on again tomorrow.
I think the problem is probably connected to the DNS. We have 2 NICs and the external was set to loopback until yesterday. Then, when checking the firewall, I reconfigured it and since then Exchange has not found the GAL, I have now set it back to loopback, but think other routing information and so on in Exchange must have been changed. I tried creating a new profile. It shows in AD users and computers, but will is not available to connect to in Outlook.
After all that, it was a Hot fix problem, solved by editing the RestrictAnonymous registry entry. I hadn't rebooted the server for around a month, until yesterday. I am assuming it only changed the registry on reboot. Everything is now OK again.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.