Slow access to CRM 3.0

[circulent]

Whether thru Outlook or just IE, access to CRM seems very slow. We have
dedicated servers for AD, and Exchange, plus CRM & SQL 2005 are on the same
box. Is there any way to optimize the performance, like with Exchange's best
practice tool?

Thanks

[John O'Donnell]

What is the hardware configuration of the crm /sql box. Also define slow..5
seconds to respond?

==============================
John O'Donnell
Microsoft CRM MVP
http://www.crowechizek.com/microsoft

"circulent" <circ...@discussions.microsoft.com> wrote in message
news:FB2647B1-BC71-417E...@microsoft.com...

[circulent]

That box is a single 3.2 GHz P4 with 1 GB RAM. 5-10 sec response

[Curt Spanburgh]

Are there customizations?

Some of these customizations start threads that need to be completed before
the next one is processed.
Have you run SQL Profiler to see what is happening while the users are
hitting the server?

[circulent]

John,

We added 1 field, and updated some of the lookup tables. Nothin crazy. We
did recently change the installed listening port from 5555 to 80. We are
having some MSCRMRouterService issues, but don't know if it's related msince
those error in the evnt log are very sporadic.

I've never heard of the SQL profiler? What is it, where can i find it, and
what do I need to do and look for? Thanks so much

Thanks

[Anne Stanton, MVP-CRM, MBA/ACC]

1 GB of RAM? Have you check to see where the bottleneck is? What about the
Hard Drives? MS CRM really does like the faster hard drives to eliminate the
most common bottleneck in most environments (I/O Bottlenecks)

--
Anne Stanton, MVP-CRM, MBA/ACC
President, The Norwich Group
http://thenorwichgroup.blogs.com/mscrm

"circulent" <circ...@discussions.microsoft.com> wrote in message

news:A1BA6A2D-1666-4A88...@microsoft.com...

[circulent]

I've checked the memory consumption on the box and its great. The hard drives
are SAAT drives on RAID 1. Is there an I/O bottleneck we should be on the
lookout for?

What's odd is that thru the browser, the speed is great. Thru Outlook its
much slower. Thoughts?

[Curt Spanburgh]

Good point Anne.

A limited amount of ram will cause a problem in the application pool, where
the threads are executed.
Good call.

"Anne Stanton, MVP-CRM, MBA/ACC" wrote:

[circulent]

what do you guys recommend?

[John O'Donnell]

if access from your web browser is fast but from outlook its slow then that
pretty much rules out a server side issue. If both web and outlook client
were slow then I would be looking at the server.

For the outlook client

1 - do all users see the problem with speed
2 - do users have large amounts of data in outlook like lots of contacts
3 - how much ram do workstations have
4 - do you use anti virus software on the workstations?

==============================
John O'Donnell
Microsoft CRM MVP
http://www.crowechizek.com/microsoft

"circulent" <circ...@discussions.microsoft.com> wrote in message

news:E1C4EB79-08AB-4F03...@microsoft.com...

[circulent]

1. Yes, all users see the problem, but it can be sporadic thru Outlook.
Sometimes slow, sometimes not
2. Each users has about 1200-1500 contacts in Outlook. That excludes the
contacts in CRM
3. Workstations have 1.0 GB RAM (min), and at least 3.0 GHz P4 machines
4. Yes, we use Symantec AV 10.0 Corprate Edition in our network

[Dan Blake (Intelligix)]

Curt,
I've had to resolve similar problems with the Outlook client for several
clients. I would recommend checking for authentication issues. If a
straight Kerberos authentication doesn't work over UDP, it goes through a
timeout period which makes the client perform sluggishly. A couple things to
check...Is the CRM web site set to accept only Integrated authentication, and
have you applied the hotfix or registry hack to force the client to use TCP
for Kerberos auth?
--
Dan Blake
Intelligix, Inc.
http://www.intelligix.com

[Curt Spanburgh]

Good point Dan.
I had a client with a misconfigured Plumtree deployment that was flooding
the segment with UDP traffic. Over a thousand UDP packets in 10 seconds and
the NIC on the server that I did the trace on was not even the destination.
This can easily break Kerberos authentication.