SPWakeUp Work Item Rss Feed

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

Commented Issue: authentication

Sharepint — Tue, 19 May 2009 08:05:40 GMT

Does not work with basic or windows authentication. Has anyone found a workaround? Thanks
Comments: ** Comment from web user: Sharepint **

For Windows Authentication, just run it as a scheduled task with the user with the correct permissions. Then start IE with the user context and add to local intranet zone.

Commented Issue: 2.3a waking up non-existent sites

enokki — Fri, 23 Jan 2009 10:12:06 GMT

I have consistently seen this problem in multiple farms at a client site.

Essentially the script "finds" and attempts to wakeup non-existent sites and subweb as described in the simulated log below:

Adding site: http://servername:8080/ssp/admin
Found subsite: http://servername:8080/ssp/admin/ssp/admin
Found subweb: http://servername:8080/ssp/admin/ssp/admin/Content
Waking up http://servername:8080/ssp/admin/ssp/admin
Cannot reach site: http://servername:8080/ssp/admin/ssp/admin
Waking up http://servername:8080/ssp/admin/ssp/admin/Content
Cannot reach site: http://servername:8080/ssp/admin/ssp/admin/Content

It looks as though it's duplicating site fragment name ssp/admin. Curious it doesn't "find" the correct path (i.e. http://servername:8080/ssp/admin and http://servername:8080/ssp/admin/Content)

Have you seen this problem, and if you have, when you plan to correct it and post the fix.

Thanks.
Comments: ** Comment from web user: enokki **

I have the same problem.
SPWakeUp adds /ssp/admin and fail to reach the site.

It runs correctly for the contents web sites, but for the SSP site, it runs poorly.
Why?

Created Issue: authentication

miketech99 — Thu, 22 Jan 2009 21:59:06 GMT

Does not work with basic or windows authentication. Has anyone found a workaround? Thanks

Commented Issue: 2.3a waking up non-existent sites

pieterw — Wed, 21 Jan 2009 07:17:29 GMT

I've experienced the same problem. It generates a lot of error's in the eventlog of our server. Please find a solution for this problem.

Created Issue: 2.3a waking up non-existent sites

efadullo — Mon, 15 Dec 2008 16:02:59 GMT

Commented Issue: Duplicating sites when unable to access a sub-site

pieterw — Wed, 12 Nov 2008 10:05:08 GMT

I just came across a bug when running against my production server's MySites. If the account running the script doesn't have access to a site, it fails when trying to read the sub-sites. I'm catching this error, but something isn't right, because it is readding the top site to the list, and building non-existent addresses then adding them to the list as well.
Obviously, I need to revisit my catch statement.

Not a show stopper of a bug. The duplicate sites are just woken more than once. The non-existent addresses are just skipped over when the address fails. Still, if you're looking to get an accurate site count, this will cause problems.
Comments: ** Comment from web user: pieterw **

Hi akennel,
Have you any idea when you are going to release a version with this bug fixed? I think this fix will solve my problem (spwakeup tries to wakeup all mysites at all sitecollections so it tries a huge amount of sites).
One other thing, can you include a version number in the properties of the executable (now you can't check the version through windows explorer).
Thanks,
Pieter

Commented Issue: Duplicating sites when unable to access a sub-site

akennel — Tue, 07 Oct 2008 19:46:43 GMT

Tracked this down finally.
SPWakeup works by building a list of web applications on a server, then checks each web app for all its Site Collections, then checks each Site Collection for all its Sub Webs. This bug arose from the code that checked Web Apps for Site Collections.
I pull a list of Site Collections by first building a new web app instance using the URL of the current listed Web App: SPWebApplication webApp = new SPSite(pullcurrentsite).WebApplication;

The problem here is my initial web app list also includes some Site Collections. So my list looks like this:
http://webapp
http://webapp/sitecollection1
http://webapp/sitecollection2
etc

When I create my new WebApp instance in the code above, I pull the current URL from my list. Since I'm building a Web App, it ignores the Site Collection portion of the URL, and just uses the webapp. That means that I end up processing the same web app multiple times.

I got around this by just doing a list.Contains check before building the webapp. That prevents the webapp from being scanned more than once. Which speeds things up considerably, and prevents those non-existent URLs from being created.

I also cleaned up some of the logging code, and eliminated an if/else statement that was never being called.

Created Issue: Duplicating sites when unable to access a sub-site

akennel — Sat, 27 Sep 2008 03:41:59 GMT

Commented Issue: SPWakeUp does not wake up site collections using Forms Authentication

akennel — Mon, 22 Sep 2008 17:19:44 GMT

The SPWakeUp script does not wake up site collections using Forms Authentication. I have placed two sites in my site.conf file: 1 Windows Authentication and 1 Forms Authentication. The script said they both successfully woken up but the Forms site didn't work.
Comments: ** Comment from web user: akennel **

I'll need to build a test server using Forms Authentication to debug this.
Not sure what kind of ETA I can give you on a fix.

Created Issue: SPWakeUp does not wake up site collections using Forms Authentication

gsaleen — Thu, 18 Sep 2008 03:43:31 GMT