SharePoint Stuff - All Comments

SharePoint Task Notifications Not Working After URL Change « Tim Lefler's IT & Security Blog

Wed, 16 Sep 2009 21:16:01 GMT

Pingback from SharePoint Task Notifications Not Working After URL Change « Tim Lefler's IT & Security Blog

Sharepoint MOSS 2007 People Search not working

Sharepoint @ decatec — Wed, 26 Aug 2009 13:31:31 GMT

re: What about PDF iFilters for MOSS 2007? (32 and 64 bit)

Jayvardhan Patil — Sun, 24 May 2009 06:36:16 GMT

Having 2-3 iFilters options in market calls for need to evaluate them.

Following are the options that are available in market

Adobe PDF iFilter 9 for 64-bit platforms

Foxit PDF IFilter

PDFlib TET PDF IFilter

While one blogger has already taken pain to evaluate them. I have converted his post into English.

Test results:

codeforfuture.com/.../finding-best-sharepoint-pdf-ifilter-64-bit

More sharepoint alert weirdness! Alert links don’t work after url change. « ….

More sharepoint alert weirdness! Alert links don’t work after url change. « …. — Tue, 05 May 2009 18:22:16 GMT

Pingback from More sharepoint alert weirdness! Alert links don’t work after url change. « ….

Understanding IIS Web Site and SharePoint Web Application « Nishant Rana’s Weblog

Sat, 25 Apr 2009 08:30:06 GMT

Pingback from Understanding IIS Web Site and SharePoint Web Application « Nishant Rana’s Weblog

Sharepoint 2007 Calendar web part connection to Exchange 2007 | keyongtech

Sharepoint 2007 Calendar web part connection to Exchange 2007 | keyongtech — Sun, 18 Jan 2009 17:17:47 GMT

Pingback from Sharepoint 2007 Calendar web part connection to Exchange 2007 | keyongtech

WSS 3.0 & MOSS: Recopilatorio de enlaces interesantes (XVIII)! « Pasi??n por la tecnolog??a…

Thu, 19 Jun 2008 22:11:28 GMT

Pingback from WSS 3.0 & MOSS: Recopilatorio de enlaces interesantes (XVIII)! « Pasi??n por la tecnolog??a…

WSS 3.0 & MOSS: Recopilatorio de enlaces interesantes (XVIII)!

Blog del CIIN — Thu, 19 Jun 2008 22:07:04 GMT

Tal y como os adelantaba en el último post , aquí tenéis la enésima entrega...bueno más bien la 18ª sobre

re: Alerts don't work after URL change

Bart Bultinck — Mon, 12 May 2008 16:20:32 GMT

impressive research... 2 thumbs up !

Search & Indexing - .MSG Outlook messages & Attachments

Office Server 2007 Ramblings — Thu, 24 Jan 2008 17:36:31 GMT

There seem to be some people in the big world of blogging that think that the correct way to get Outlook

MOSS Search for emails and attachments context

Dirk Van den Berghe SharePoint Admin Blog — Thu, 17 Jan 2008 08:53:16 GMT

found this article on: lirliron.blogspot.com/.../moss-search-for-emails-and-attachments.html

MOSS Search for emails and attachments context

Mirrored Blogs — Wed, 16 Jan 2008 13:34:32 GMT

Some of our customers requested to have the ability to search context within email messages and within

A Sharepoint Legend : One Web Application = One Content Database

Blog de Jérémie Clabaut (ak MinSou) — Tue, 18 Dec 2007 16:03:33 GMT

Today I heard from a "Sharepoint Expert" that we can create only one content database per web application on Sharepoint. From an expert, It makes me laugh Tom Vandaele explains (better than me ) on his blog why this assertion is false ! &#1

re: KB934525 screwed things up...

Tom Vandaele — Wed, 07 Nov 2007 19:22:24 GMT

I do hope that your description helps others with the same problem.

We were in the great situation that

1. the content we needed was still intact

2. the new portal wasn't used yet (clean install)

3. we were migrating servers at that time

Thanks to that situation, we could start over again, with a fresh install without having to apply that update again. (Btw, it also installed due to an automatic update) For us, this was the best solution.

Unfortunately, not everyone is in this situation. For now, I advice people to turn automatic updates off and I hope Service Pack 1 will be kick-ass :-)

re: KB934525 screwed things up...

marcovanschagen — Wed, 07 Nov 2007 08:40:10 GMT

Hi,

We have experienced a site down situation a few weeks ago. We consulted Microsoft on this and actually had a good lengthy session with the engineers. We got it back to working order without reinstall of all the things. I'll log what we have done as parts of it may be of use to you.

We found out a hotfix was loaded with Windows Update, this is the Cumulative Security Update for Windows SharePoint Services 3.0 (KB934525). This loaded itself on october, 10, 2007.

So, we found our websites non responsive, Central Admin is non responsive, and via the management console we were not able to enter

the IIS tree. We found out, the IIS Admin Service was marked as Stopping, but did not stop. We did an IISReset to help the service

stop and restart. IIS is then accessible.

Then we found the SharePoint content database was still inaccessible, found out it was locked to single user. Trying to reboot does not help, still Cannot Connect to Config Database.Then set the database back to multi user with the SQL management studio (or use query analyser) command: ALTER DATABASE [SharePoint_Config_--your guid here--] SET MULTI_USER -Note, this will probably fail for the database is locked by an other process; find the process number in your current activity and add this line before the command: KILL nn where nn is the process number. Execute both lines in one go. So now

the database is back to normal use.

Still the site does not want to come back. That is when we entered the conference call with Microsoft. Looked at a whole lot of stuff.

Decided the HotFix update did not install correctly, so we tried an inplace forced upgrade of the databases.

(open a cmd, go to your sharepoint folder) PSCONFIG -cmd upgrade

-inplace b2b -wait -force

Sat back a long time while it is working on all those tasks. It came back with an error (on hind sight this may be faillure on our system to get the services restarted) Then did an IISRESET again, sites were back and operational.

Figured since we had an error, we needed to better confirm things.

There is also in your programs menu a UI command to perform an update

- this does include checking and setting more options compared to the commantline call. We ran this, and sat back. Still an error, in step 10, the last step getting the services back to live. We did spend some time on this error, but basically this was not needed. IISRESET does the trick bringing the services back to live.

We think for some reason, the hotfix failed, and did not perform an update on the databases. You can do this manually as described.

Also we experience a problem with the automated restart of IIS, having the service marked as 'stopping' for forever, and causing a timeout on whatever is waiting (try to do an IISRESET when you see this happen, before the timeout) - we think we may run into trouble for the next hotfix, but that is an other story.

I hope this description helps you.