SPWakeUp - Wake up your Sharepoint and WSS Sites

Created Release: 2.4 (Nov 13, 2009)

akennel — Fri, 13 Nov 2009 18:10:01 GMT

New features added. Now supports setting login name and password at run time. Also supports Basic and Digest authentication in addition to NTLM.

The new authentication code was created by Rafale. Many thanks for the addition!

Released: 2.4 (Nov 13, 2009)

Fri, 13 Nov 2009 18:10:01 GMT

New Post: https

simonjking — Tue, 20 Oct 2009 23:19:09 GMT

all over it, just been hectic - will look to put the rest up this weekend.

From: [email removed]
To: [email removed]
Date: Fri, 16 Oct 2009 07:56:38 -0700
Subject: Re: https [SPWakeUp:49282]

From: punishyourmachine

Hello. I have just started to use this tool to wake up our Sharepoint farm in the mornings before the business users arrive. It's working great for our internal HTTP web app. But we now have a 2nd web app that is HTTPS, and I am also getting the error on how it won't wake up HTTPS. Any update as to when/if a new version that can handle HTTPS will be released? Thanks!

Read the full discussion online.
To add a post to this discussion, reply to this email (SPWakeUp@discussions.codeplex.com)
To start a new discussion for this project, email SPWakeUp@discussions.codeplex.com
You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.
Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

Windows Live: Keep your friends up to date with what you do online.

New Post: https

punishyourmachine — Fri, 16 Oct 2009 14:56:31 GMT

New Post: https

chapyn — Mon, 28 Sep 2009 00:18:24 GMT

thank you

New Post: https

simonjking — Sun, 27 Sep 2009 22:27:47 GMT

I have a solution, which we are testing in the next week - initial testing passed, and then will look at uploading the code and working with the people that created the original files - will keep you posted.

Created Issue: https not working... [5001]

chapyn — Sun, 27 Sep 2009 21:31:39 GMT

My log file :
Web Application discovery set to on.
Found 2 Site Collections.
Waking up 2 sites.
Waking up https://wss.domain.com
Error: https://wss.domain.com could not be reached
Waking up https://wss.domain.com/sites/test2
Error: https://wss.domain.com/sites/test2 could not be reached

New Post: https

chapyn — Sun, 27 Sep 2009 21:28:41 GMT

I have also the same issue anyone have the solution?

New Post: https

simonjking — Mon, 31 Aug 2009 03:29:42 GMT

is there going to be a response to this question

New Post: Error: Cannot reach site

cccsec — Mon, 29 Jun 2009 08:57:45 GMT

By the way, the same issue caused caused all crawls to fail on sites with names other than the native host name of the sharepoint server. So, sharepoint search was affected by the same issue.

New Post: Error: Cannot reach site

cccsec — Sat, 27 Jun 2009 23:26:34 GMT

Praise eezz (and akennel, of course ;-) Method 2 of kb896861 solved it for me too!

New Post: Error: Cannot reach site

gary99 — Tue, 23 Jun 2009 17:33:35 GMT

Thanks - that reghack does seem to have fixed the problem.

New Post: Error: Cannot reach site

eezz — Wed, 10 Jun 2009 23:43:46 GMT

Here is the link... http://support.microsoft.com/kb/896861

I tried Method 1 but it didn't work for me... so I used Method 2!

New Post: Error: Cannot reach site

ecrane — Wed, 10 Jun 2009 16:58:12 GMT

How did you disable the loopback check? I'm not familiar with this.

New Post: Error: Cannot reach site

eezz — Wed, 10 Jun 2009 01:32:36 GMT

Hi,

I was also confronted by this issue. After a bit of poking around I found heaps of 537 events in the Security event logs. I then disabled the loopback check and it works fine now, I hope this helps to solve some of the similar issues that appear to be facing some users.

New Post: Error: Cannot reach site

eezz — Wed, 10 Jun 2009 01:32:36 GMT

Hi,

New Post: Woken Up?

crankypants — Wed, 03 Jun 2009 15:02:05 GMT

Hi,

First off, I love the concept of this and hope I can get it working... my users would be very happy.

I'm running WSSv3 on Win2008. I've scheduled the .exe to run every morning with the following parameters:

-site:http://myserverhostname -discover -log:c:\schedule\sp_wakeup_log.txt

The schedule runs and the log states:

Web Application discovery set to on.
Found 1 Site Collections.
Waking up 85 sites.

..... all woken successfully.

I'm not using sites.conf or the exclusion file.

However, when I bring up the parent site and subsites, they still seem to take a while to load, as if they've never been woken up. As expected, subsequent hits on the sites are speedy.

Am I missing something?

Thanks for any input.

New Post: Error: Cannot reach site

ecrane609 — Wed, 03 Jun 2009 14:32:30 GMT

well I am using host headers too. They get enemerated but cannot be reached either

New Post: Error: Cannot reach site

gary99 — Wed, 03 Jun 2009 14:04:23 GMT

I have recieved the same errors. could it have anything to do with host headers? On my VMs that do not use host headers it seems to work fine, but on those with HH - I get the sites enumerated, but they cannot be reached.

New Post: Does SPWakeUp break your Microsoft support rights on MOSS?

amleth — Wed, 27 May 2009 02:28:16 GMT

The underlying SharePoint API used by spwakeup.exe does require some database privileges to run.

You can use the server farm account to run spwakeup.exe -- that should solve your permissions issues.