RE: Outlook address resolution SO SLOW

2002-01-17 Thread Roger Mackenzie

Paul,

Thanks for this; I avoided O2K as it needs the admin kit (is that
the name) to install on TS but Outlook98 installs apparently OK. The
symptoms you describe are very similar. When you say 'transformed', what are
you referring to?

Cheers, Roger

-Original Message-
From: Paul Bouzan [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2002 12:07
To: Exchange Discussions
Subject: RE: Outlook address resolution SO SLOW


Was Outlook Transformed to work with TS?

We use W2K AS with TS to provide our Accounts with the means to run a legacy
Access database that has grown so fat it needs a dual 1Gig + 512Mb RAM to
process the queries (yes, I know - what a waste but the migration to SQL is
happening slowly).

Anyway back to the point.  Fire up Access in a TS session and all is well
and good.  Fire up Access as an App on the server and it runs like a
two-legged hamster.  O2K had to be transformed to work with TS - I not know
if other office versions need this but does any of it fit with your
predicament Roger?

PBB
~ndi


-Original Message-
From: Roger Mackenzie [mailto:[EMAIL PROTECTED]] 
Sent: 17 January 2002 12:04
To: Exchange Discussions
Subject: RE: Outlook address resolution SO SLOW


just did, less than 10 ms.

-Original Message-
From: Busby, Jacob [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2002 10:37
To: Exchange Discussions
Subject: RE: Outlook address resolution SO SLOW


Dumb question, but have you tried pinging your server and checking the
response time?

 -Original Message-
 From: Roger Mackenzie [mailto:[EMAIL PROTECTED]]
 Sent: 17 January 2002 10:32
 To: Exchange Discussions
 Subject: Outlook address resolution SO SLOW
 
 
 Folks,
 
   Does anyone recognise this bizarre situation.
 
   Outlook 98 on a NT4 Terminal Server (hosting a witches
 brew of other
 applications to do with telephone logging). MAPI profile connecting an
 Exchange 5.5 SP3 + store fix. Console auto logs in to run telephone
 statistics collection and uses Outlook 98 for the purposes of 
 e-mailing
 reports. If you manually send mail to GAL entries, no problem. If you
 manually send mail to an SMTP address ([EMAIL PROTECTED]) the Outlook process
 freezes as you type the '@' (this is not displayed) and task 
 manager shows
 it burning lots of cpu. It eventually returns control. The 
 automated report
 mailing process by necessity uses SMTP addresses and times out the
 application. Bizarrely if you check the properties of any of 
 the standard
 folders they do not display permissions tabs, synchronisation 
 tab etc as if
 the folders were based on a PST.
 
   BUT if you login to the same user via the TS client
 service, Outlook
 98, using the same mail profile behaves completely normally!
 
   As this is a live logging service with bundles of bespoke 
 applications I'm completely stuffed when it comes to experimenting 
 with the service.
 
   Any thoughts?
 
 Regards, Roger Mackenzie (Glasgow University)
 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Outlook address resolution SO SLOW

2002-01-17 Thread Paul Bouzan

Roger,

I haven't had the pleasure of installing any version of office previous to
2K on a TS so I wouldn't know if anything had to be done via an admin kit or
transform file (quite likely the same), sorry.  Hopefully someone else on
the list might be able to shed some light on the matter.  If previous
versions have to be transformed to work with TS then we might have some more
luck...

I would look into Dominic's suggestion of the profiles possibly having an
effect as this may help.

Regards

PBB
~ndi


-Original Message-
From: Roger Mackenzie [mailto:[EMAIL PROTECTED]] 
Sent: 17 January 2002 13:39
To: Exchange Discussions
Subject: RE: Outlook address resolution SO SLOW


Paul,

Thanks for this; I avoided O2K as it needs the admin kit (is that
the name) to install on TS but Outlook98 installs apparently OK. The
symptoms you describe are very similar. When you say 'transformed', what are
you referring to?

Cheers, Roger

-Original Message-
From: Paul Bouzan [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2002 12:07
To: Exchange Discussions
Subject: RE: Outlook address resolution SO SLOW


Was Outlook Transformed to work with TS?

We use W2K AS with TS to provide our Accounts with the means to run a legacy
Access database that has grown so fat it needs a dual 1Gig + 512Mb RAM to
process the queries (yes, I know - what a waste but the migration to SQL is
happening slowly).

Anyway back to the point.  Fire up Access in a TS session and all is well
and good.  Fire up Access as an App on the server and it runs like a
two-legged hamster.  O2K had to be transformed to work with TS - I not know
if other office versions need this but does any of it fit with your
predicament Roger?

PBB
~ndi


-Original Message-
From: Roger Mackenzie [mailto:[EMAIL PROTECTED]] 
Sent: 17 January 2002 12:04
To: Exchange Discussions
Subject: RE: Outlook address resolution SO SLOW


just did, less than 10 ms.

-Original Message-
From: Busby, Jacob [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2002 10:37
To: Exchange Discussions
Subject: RE: Outlook address resolution SO SLOW


Dumb question, but have you tried pinging your server and checking the
response time?

 -Original Message-
 From: Roger Mackenzie [mailto:[EMAIL PROTECTED]]
 Sent: 17 January 2002 10:32
 To: Exchange Discussions
 Subject: Outlook address resolution SO SLOW
 
 
 Folks,
 
   Does anyone recognise this bizarre situation.
 
   Outlook 98 on a NT4 Terminal Server (hosting a witches
 brew of other
 applications to do with telephone logging). MAPI profile connecting an 
 Exchange 5.5 SP3 + store fix. Console auto logs in to run telephone 
 statistics collection and uses Outlook 98 for the purposes of 
 e-mailing reports. If you manually send mail to GAL entries, no 
 problem. If you manually send mail to an SMTP address ([EMAIL PROTECTED]) the 
 Outlook process freezes as you type the '@' (this is not displayed) 
 and task manager shows
 it burning lots of cpu. It eventually returns control. The 
 automated report
 mailing process by necessity uses SMTP addresses and times out the
 application. Bizarrely if you check the properties of any of 
 the standard
 folders they do not display permissions tabs, synchronisation 
 tab etc as if
 the folders were based on a PST.
 
   BUT if you login to the same user via the TS client
 service, Outlook
 98, using the same mail profile behaves completely normally!
 
   As this is a live logging service with bundles of bespoke
 applications I'm completely stuffed when it comes to experimenting 
 with the service.
 
   Any thoughts?
 
 Regards, Roger Mackenzie (Glasgow University)
 

___

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Outlook address resolution SO SLOW

2002-01-17 Thread Nick Field

Long shot here, but have you checked the location and accessibility of the
address lists that the client uses for 'auto' name resolution?

Nick

-Original Message-
From: Roger Mackenzie [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, January 17, 2002 10:32 AM
To: Exchange Discussions
Subject: Outlook address resolution SO SLOW

Folks,

Does anyone recognise this bizarre situation.

Outlook 98 on a NT4 Terminal Server (hosting a witches brew of other
applications to do with telephone logging). MAPI profile connecting an
Exchange 5.5 SP3 + store fix. Console auto logs in to run telephone
statistics collection and uses Outlook 98 for the purposes of e-mailing
reports. If you manually send mail to GAL entries, no problem. If you
manually send mail to an SMTP address ([EMAIL PROTECTED]) the Outlook process
freezes as you type the '@' (this is not displayed) and task manager shows
it burning lots of cpu. It eventually returns control. The automated report
mailing process by necessity uses SMTP addresses and times out the
application. Bizarrely if you check the properties of any of the standard
folders they do not display permissions tabs, synchronisation tab etc as if
the folders were based on a PST.

BUT if you login to the same user via the TS client service, Outlook
98, using the same mail profile behaves completely normally!

As this is a live logging service with bundles of bespoke
applications I'm completely stuffed when it comes to experimenting with the
service.

Any thoughts?

Regards, Roger Mackenzie (Glasgow University)

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]