| Author |
Message |
Donald J. Lindstrom
Guest
|
 Posted:
Fri Nov 25, 2005 9:58 am Post subject:
$problems after system crash - clients cannot connect |
|
|
After a power cycle, a client's Dell 2600 (Windows SBS2000) started finding
new hardware - it got really bad as it started discovering PCI bridges and
etc.
to make a long story short, had to do a "repair" to windows with disk1, then
re-apply patches, updates, etc. Initially Exchange Mail Store would not mount
but found a reg hack fix for some missing reg entries on MS site, so got the
stores mounted.
Now, client PCs (Outlook) cannot connect and open their mailboxes. The msg
says the folders cannot open and the server is unavailable (interesting
enough, you can define a new account, resolve the name in setup, etc)...
I don't see anything of interest in either event logs.
I also just tried to run Exchange Best Practices, but it stops after about 5
seconds and says the user has aborted it.
I think my exchange is sick, wondering if anyone has any ideas.
BTW, OWA works fine if that helps.
TIA,
Don
|
|
| Back to top |
|
 |
Tom Felts
Guest
|
| Posted:
Fri Nov 25, 2005 4:35 pm Post subject:
Re: $problems after system crash - clients cannot connect |
|
|
Here is a link to an article that discusses how to re-install exchange on
SBS: http://support.microsoft.com/default.aspx?scid=kb%3B[LN]%3BQ320202
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote in
message news:3B61C406-80C7-4134-86CE-3CBA481C1C73@microsoft.com...
| Quote: | After a power cycle, a client's Dell 2600 (Windows SBS2000) started
finding
new hardware - it got really bad as it started discovering PCI bridges and
etc.
to make a long story short, had to do a "repair" to windows with disk1,
then
re-apply patches, updates, etc. Initially Exchange Mail Store would not
mount
but found a reg hack fix for some missing reg entries on MS site, so got
the
stores mounted.
Now, client PCs (Outlook) cannot connect and open their mailboxes. The msg
says the folders cannot open and the server is unavailable (interesting
enough, you can define a new account, resolve the name in setup, etc)...
I don't see anything of interest in either event logs.
I also just tried to run Exchange Best Practices, but it stops after about
5
seconds and says the user has aborted it.
I think my exchange is sick, wondering if anyone has any ideas.
BTW, OWA works fine if that helps.
TIA,
Don
|
|
|
| Back to top |
|
|
Donald J. Lindstrom
Guest
|
| Posted:
Sat Nov 26, 2005 8:55 am Post subject:
Re: $problems after system crash - clients cannot connect |
|
|
Well, I went through that whole process and the problem remains. I tried also
creating a new user in ad (and created a mailbox) and logging into a
workstation with the new user name and configured outlook. When tryinhg to
open Outlook after configuring, it says "unable to open your default email
folders. YOu must connect to your MIcrosft Exchange Server with the current
profile before you can synchronize your folders with your offline folder
files".
That sounds like a OST file thing.
Bottom line is IU am still open to suggestions.
TIA,
Don
"Tom Felts" wrote:
| Quote: | Here is a link to an article that discusses how to re-install exchange on
SBS: http://support.microsoft.com/default.aspx?scid=kb%3B[LN]%3BQ320202
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote in
message news:3B61C406-80C7-4134-86CE-3CBA481C1C73@microsoft.com...
After a power cycle, a client's Dell 2600 (Windows SBS2000) started
finding
new hardware - it got really bad as it started discovering PCI bridges and
etc.
to make a long story short, had to do a "repair" to windows with disk1,
then
re-apply patches, updates, etc. Initially Exchange Mail Store would not
mount
but found a reg hack fix for some missing reg entries on MS site, so got
the
stores mounted.
Now, client PCs (Outlook) cannot connect and open their mailboxes. The msg
says the folders cannot open and the server is unavailable (interesting
enough, you can define a new account, resolve the name in setup, etc)...
I don't see anything of interest in either event logs.
I also just tried to run Exchange Best Practices, but it stops after about
5
seconds and says the user has aborted it.
I think my exchange is sick, wondering if anyone has any ideas.
BTW, OWA works fine if that helps.
TIA,
Don
|
|
|
| Back to top |
|
|
Tom Felts
Guest
|
| Posted:
Sat Nov 26, 2005 9:58 am Post subject:
Re: $problems after system crash - clients cannot connect |
|
|
What happens if you create a new user, (which you did already) and then
create a new profile with no ost? Will that open the mailbox? What version
of outlook are you using, and how are profiles generated for users?
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote in
message news:5665CCB9-0949-408F-9D3F-DCD8F8A23EEA@microsoft.com...
| Quote: | Well, I went through that whole process and the problem remains. I tried
also
creating a new user in ad (and created a mailbox) and logging into a
workstation with the new user name and configured outlook. When tryinhg to
open Outlook after configuring, it says "unable to open your default email
folders. YOu must connect to your MIcrosft Exchange Server with the
current
profile before you can synchronize your folders with your offline folder
files".
That sounds like a OST file thing.
Bottom line is IU am still open to suggestions.
TIA,
Don
"Tom Felts" wrote:
Here is a link to an article that discusses how to re-install exchange
on
SBS: http://support.microsoft.com/default.aspx?scid=kb%3B[LN]%3BQ320202
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote
in
message news:3B61C406-80C7-4134-86CE-3CBA481C1C73@microsoft.com...
After a power cycle, a client's Dell 2600 (Windows SBS2000) started
finding
new hardware - it got really bad as it started discovering PCI bridges
and
etc.
to make a long story short, had to do a "repair" to windows with
disk1,
then
re-apply patches, updates, etc. Initially Exchange Mail Store would
not
mount
but found a reg hack fix for some missing reg entries on MS site, so
got
the
stores mounted.
Now, client PCs (Outlook) cannot connect and open their mailboxes. The
msg
says the folders cannot open and the server is unavailable
(interesting
enough, you can define a new account, resolve the name in setup,
etc)...
I don't see anything of interest in either event logs.
I also just tried to run Exchange Best Practices, but it stops after
about
5
seconds and says the user has aborted it.
I think my exchange is sick, wondering if anyone has any ideas.
BTW, OWA works fine if that helps.
TIA,
Don
|
|
|
| Back to top |
|
|
Donald J. Lindstrom
Guest
|
| Posted:
Sun Nov 27, 2005 9:58 am Post subject:
Re: $problems after system crash - clients cannot connect |
|
|
First, thanks for the help Tom.
I tried that - made no differnence - I have gotten a little closer though.
It has to do with RPC. I had a problem with the event log, which when fixed
gave me:
An RPC communications error occurred. An attempt to listen over RPC has
failed. Windows 2000 Error: 1703. [ncanc_ip_tcp BASE IL MAIN BASE 1 504] (14)
This is being reported from MSExchangeMTA EventID: 9321.
I have been searching WWW threads and been in the registry - this error
points back to the registry entries I had to put into the
HKLM/SW/MS/RPC/CLIENTPROTOCOLS....
I have checked syntax, permissions of these keys, binding orders, etc. and
I am sure I am close here. Just missing something.
Don
"Tom Felts" wrote:
| Quote: | What happens if you create a new user, (which you did already) and then
create a new profile with no ost? Will that open the mailbox? What version
of outlook are you using, and how are profiles generated for users?
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote in
message news:5665CCB9-0949-408F-9D3F-DCD8F8A23EEA@microsoft.com...
Well, I went through that whole process and the problem remains. I tried
also
creating a new user in ad (and created a mailbox) and logging into a
workstation with the new user name and configured outlook. When tryinhg to
open Outlook after configuring, it says "unable to open your default email
folders. YOu must connect to your MIcrosft Exchange Server with the
current
profile before you can synchronize your folders with your offline folder
files".
That sounds like a OST file thing.
Bottom line is IU am still open to suggestions.
TIA,
Don
"Tom Felts" wrote:
Here is a link to an article that discusses how to re-install exchange
on
SBS: http://support.microsoft.com/default.aspx?scid=kb%3B[LN]%3BQ320202
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote
in
message news:3B61C406-80C7-4134-86CE-3CBA481C1C73@microsoft.com...
After a power cycle, a client's Dell 2600 (Windows SBS2000) started
finding
new hardware - it got really bad as it started discovering PCI bridges
and
etc.
to make a long story short, had to do a "repair" to windows with
disk1,
then
re-apply patches, updates, etc. Initially Exchange Mail Store would
not
mount
but found a reg hack fix for some missing reg entries on MS site, so
got
the
stores mounted.
Now, client PCs (Outlook) cannot connect and open their mailboxes. The
msg
says the folders cannot open and the server is unavailable
(interesting
enough, you can define a new account, resolve the name in setup,
etc)...
I don't see anything of interest in either event logs.
I also just tried to run Exchange Best Practices, but it stops after
about
5
seconds and says the user has aborted it.
I think my exchange is sick, wondering if anyone has any ideas.
BTW, OWA works fine if that helps.
TIA,
Don
|
|
|
| Back to top |
|
|
Tom Felts
Guest
|
| Posted:
Sun Nov 27, 2005 9:58 am Post subject:
Re: $problems after system crash - clients cannot connect |
|
|
What entries did you put in? Binding order is significant. You can also
use rpc ping to test rpc
connectivity...http://www.microsoft.com/windows2000/techinfo/reskit/tools/ex
isting/rpcping-o.asp
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote in
message news:24E9105E-46D9-4271-A1CC-A1A22D6B42E2@microsoft.com...
| Quote: | First, thanks for the help Tom.
I tried that - made no differnence - I have gotten a little closer
though.
It has to do with RPC. I had a problem with the event log, which when
fixed
gave me:
An RPC communications error occurred. An attempt to listen over RPC has
failed. Windows 2000 Error: 1703. [ncanc_ip_tcp BASE IL MAIN BASE 1 504]
(14)
This is being reported from MSExchangeMTA EventID: 9321.
I have been searching WWW threads and been in the registry - this error
points back to the registry entries I had to put into the
HKLM/SW/MS/RPC/CLIENTPROTOCOLS....
I have checked syntax, permissions of these keys, binding orders, etc.
and
I am sure I am close here. Just missing something.
Don
"Tom Felts" wrote:
What happens if you create a new user, (which you did already) and then
create a new profile with no ost? Will that open the mailbox? What
version
of outlook are you using, and how are profiles generated for users?
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote
in
message news:5665CCB9-0949-408F-9D3F-DCD8F8A23EEA@microsoft.com...
Well, I went through that whole process and the problem remains. I
tried
also
creating a new user in ad (and created a mailbox) and logging into a
workstation with the new user name and configured outlook. When
tryinhg to
open Outlook after configuring, it says "unable to open your default
email
folders. YOu must connect to your MIcrosft Exchange Server with the
current
profile before you can synchronize your folders with your offline
folder
files".
That sounds like a OST file thing.
Bottom line is IU am still open to suggestions.
TIA,
Don
"Tom Felts" wrote:
Here is a link to an article that discusses how to re-install
exchange
on
SBS:
http://support.microsoft.com/default.aspx?scid=kb%3B[LN]%3BQ320202
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com
wrote
in
message news:3B61C406-80C7-4134-86CE-3CBA481C1C73@microsoft.com...
After a power cycle, a client's Dell 2600 (Windows SBS2000)
started
finding
new hardware - it got really bad as it started discovering PCI
bridges
and
etc.
to make a long story short, had to do a "repair" to windows with
disk1,
then
re-apply patches, updates, etc. Initially Exchange Mail Store
would
not
mount
but found a reg hack fix for some missing reg entries on MS site,
so
got
the
stores mounted.
Now, client PCs (Outlook) cannot connect and open their mailboxes.
The
msg
says the folders cannot open and the server is unavailable
(interesting
enough, you can define a new account, resolve the name in setup,
etc)...
I don't see anything of interest in either event logs.
I also just tried to run Exchange Best Practices, but it stops
after
about
5
seconds and says the user has aborted it.
I think my exchange is sick, wondering if anyone has any ideas.
BTW, OWA works fine if that helps.
TIA,
Don
|
|
|
| Back to top |
|
|
Donald J. Lindstrom
Guest
|
| Posted:
Thu Dec 08, 2005 1:59 am Post subject:
Re: $problems after system crash - clients cannot connect |
|
|
Hey Tom, sorry I did not finish this thread sooner. It was something in the
registry to do with the binding orders. I finally had to throw in the towel
and call MS. Unfortunately, the engineer used RDP to get to the server and
not LiveMeeting so I never saw exactly what he fiddled with - again, thank
you very much for your help.
Don
"Tom Felts" wrote:
| Quote: | What entries did you put in? Binding order is significant. You can also
use rpc ping to test rpc
connectivity...http://www.microsoft.com/windows2000/techinfo/reskit/tools/ex
isting/rpcping-o.asp
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote in
message news:24E9105E-46D9-4271-A1CC-A1A22D6B42E2@microsoft.com...
First, thanks for the help Tom.
I tried that - made no differnence - I have gotten a little closer
though.
It has to do with RPC. I had a problem with the event log, which when
fixed
gave me:
An RPC communications error occurred. An attempt to listen over RPC has
failed. Windows 2000 Error: 1703. [ncanc_ip_tcp BASE IL MAIN BASE 1 504]
(14)
This is being reported from MSExchangeMTA EventID: 9321.
I have been searching WWW threads and been in the registry - this error
points back to the registry entries I had to put into the
HKLM/SW/MS/RPC/CLIENTPROTOCOLS....
I have checked syntax, permissions of these keys, binding orders, etc.
and
I am sure I am close here. Just missing something.
Don
"Tom Felts" wrote:
What happens if you create a new user, (which you did already) and then
create a new profile with no ost? Will that open the mailbox? What
version
of outlook are you using, and how are profiles generated for users?
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com> wrote
in
message news:5665CCB9-0949-408F-9D3F-DCD8F8A23EEA@microsoft.com...
Well, I went through that whole process and the problem remains. I
tried
also
creating a new user in ad (and created a mailbox) and logging into a
workstation with the new user name and configured outlook. When
tryinhg to
open Outlook after configuring, it says "unable to open your default
email
folders. YOu must connect to your MIcrosft Exchange Server with the
current
profile before you can synchronize your folders with your offline
folder
files".
That sounds like a OST file thing.
Bottom line is IU am still open to suggestions.
TIA,
Don
"Tom Felts" wrote:
Here is a link to an article that discusses how to re-install
exchange
on
SBS:
http://support.microsoft.com/default.aspx?scid=kb%3B[LN]%3BQ320202
"Donald J. Lindstrom" <DonaldJLindstrom@discussions.microsoft.com
wrote
in
message news:3B61C406-80C7-4134-86CE-3CBA481C1C73@microsoft.com...
After a power cycle, a client's Dell 2600 (Windows SBS2000)
started
finding
new hardware - it got really bad as it started discovering PCI
bridges
and
etc.
to make a long story short, had to do a "repair" to windows with
disk1,
then
re-apply patches, updates, etc. Initially Exchange Mail Store
would
not
mount
but found a reg hack fix for some missing reg entries on MS site,
so
got
the
stores mounted.
Now, client PCs (Outlook) cannot connect and open their mailboxes.
The
msg
says the folders cannot open and the server is unavailable
(interesting
enough, you can define a new account, resolve the name in setup,
etc)...
I don't see anything of interest in either event logs.
I also just tried to run Exchange Best Practices, but it stops
after
about
5
seconds and says the user has aborted it.
I think my exchange is sick, wondering if anyone has any ideas.
BTW, OWA works fine if that helps.
TIA,
Don
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in