I had a real problem after installing WDS 2.x, the CPU would peg at 99% for
long periods of time. Indows Indexing Service was presumably the culprit. I
finally disabled it.

I got a note from MS support (via connect) that WDS 3.0 would fix the issue,
so I installed WDS 3.0 when ON2007 B2TR came out.

I am still getting long periods of 100% CPU due to the cisvc.exe running.

Anyone else experiencing this?

Is this cisvc.exe needed for WDS 3.0, or is this a remnant from the past
that I can try to disable?

Thanks,

Did you remove WDS 2?
I don't even know what civsvc.exe, so this could be WDS 2 (or something
else).

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007: http://pschmid.net/office2007/customize
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed

"GobinderConvert?" <GobinderConvert@discussions.microsoft.com> wrote in
message news:CCEA6FAE-77B0-482F-911C-565275EDA88A@microsoft.com:

> I had a real problem after installing WDS 2.x, the CPU would peg at 99% for
> long periods of time. Indows Indexing Service was presumably the culprit. I
> finally disabled it.
>
> I got a note from MS support (via connect) that WDS 3.0 would fix the issue,
> so I installed WDS 3.0 when ON2007 B2TR came out.
>
> I am still getting long periods of 100% CPU due to the cisvc.exe running.
>
> Anyone else experiencing this?
>
> Is this cisvc.exe needed for WDS 3.0, or is this a remnant from the past
> that I can try to disable?
>
> Thanks,

"GobinderConvert?" wrote:

> I had a real problem after installing WDS 2.x, the CPU would peg at 99% for
> long periods of time. Indows Indexing Service was presumably the culprit. I
> finally disabled it.

Yep. I seem to be having the same problem. I have a fresh install of XP
(tablet pc edition), fesh install of Onenote 2007 w/beta refresh, and fresh
install of WDS 3.0.

It seems like I am hitting a race condition. The last time it happened, I
was making simple boxes for network diagrams and dragging-and-dropping them
around in Onenote, then the indexing thread kicks off and I seem to be
deadlocked in Onenote.

I had a couple of these CPU pegs in a row for 20 minutes at a time. Finally
Onenote gave up, and crashed. I believe the developers should have received
my crash output automatically.

-Steve

I've been having the same issues with cisvc.exe pegging out on my TabletPC. It is very random and acts up even if I'm not in an application. I had this issue in the past when I installed windows desktop search about 6 months ago.

My fix was to uninstall windows desktop search and go with googles search. The issue now is that the indexing is so closely tied to Office 2007 that it's not the best option.

- dsm

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

How long did you let indexing run before you gave up on it? I have found
that letting the indexing run for a couple of days seems to make this
better. In addition, I have noticed that the processor spikes at some point
after I do a large Print to OneNote....

Just my two cents.

--
Kathy Jacobs, Microsoft MVP OneNote and PowerPoint
Author of Kathy Jacobs on PowerPoint
Get PowerPoint and OneNote information at www.onppt.com

I believe life is meant to be lived. But:
if we live without making a difference, it makes no difference that we lived

"D. Menefee" wrote in message news:20071289639douglobb******.com...
> I've been having the same issues with cisvc.exe pegging out on my
> TabletPC. It is very random and acts up even if I'm not in an application.
> I had this issue in the past when I installed windows desktop search about
> 6 months ago.
>
> My fix was to uninstall windows desktop search and go with googles search.
> The issue now is that the indexing is so closely tied to Office 2007 that
> it's not the best option.
>
> - dsm
>
> EggHeadCafe.com - .NET Developer Portal of Choice
> http://www.eggheadcafe.com