To all the early adopters clients, partners, vendors mentors, bloggers and of course friends Mindy, Luc, Jeremy, Gemma, Oleg K, Oleg L, Tatiana, Frank M, Benjamin G,  Andy, Mike D, Cameron F, Lance, Frank G, Karen O, Scott M, Scott J, Todd M, Brian, Tolga, Francis, Maurice, Jim, Richard K, Guy, G, Michael T, Glenn H, David U, Tim E, Kimberly, Sergiy, Christina, Aaron and all the folks that I have had the opportunity and pleasure to work with as early adopters of SharePoint 2007, Project Server 2007 @ ScriptLogic, WATG, DigitalGlobe, Northrop Grumman, FijiWater, Roll International, Money Mailer, Orange County Fire Authority. Cadence Design Systems, Ontolica, CorasWorks, MetaLogix, Dockit, Tzunami, Bamboo Solutions, iDevfactory, Citrix, SPSDev.com, Advis, Houlihan Lokey, Motion Picture Association of America, Integration Technologies inc, Neudesic, EMC and many more.... I can’t help but think back to my first experiences with SharePoint in 2002 with Warner Bros and how cool it was to create project sites for the storage and retrieval of Project documentation Al , Jim, Harold, Steven, Sean, Cad, and Larry I will always love you guys and thank you for your support WB is the place to be......

Lastly, the people who made the impossible possible by sharing their knowledge with the rest of us when there were not any sources of information besides the SharePoint Products and Technologies Resource Kit by Bill English. Maurice Prather, Bob Mixon, Andrew Connell, Heather Solomon, Todd Baginski, Mike Fitzmaurice, Jim Duncan, Renaud Comte, Jan Tielens, Mark Kruger, Andrew May, Arpan Shah, Bil Simser, Carlos Segura, Joel Oleson, Keith Richie, Mart Muller, Michael Blumenthal, Mike Hodnick, Mike Walsh, Todd Bleeker, Mark Harrison thats all I remember off the top of my head. I know there were many more and millions now, they say the mind the first to go, lol...

SP1 definitely is a huge step in the right direction, improves performance, and I am sure you will notice as we have discussed many times from performance with X64 to duplicates in search for people,  having to use stsadm to start the search query service with the and associate the query role when deployed in a farm where your WFEs are also query servers. and many more....

However, if you have installed Project Server 2007 in your SharePoint 2007 environment be careful and test comprehensively in development prior to deploying in production. I installed the SP by using Microsoft Update to download and install the 2007 Microsoft Office System Servers Service Pack 1 (SP1). The project server dbs were corrupted and I received the following error in the event log. The quick resolution for me since its a dev environment on my laptop was to create a new SSP, spin up a new PWA location and create the new dbs. Obviously this will not work in prod..... i am in the research phase spinning up a few VMs and will post more info once I have the research complete. I will be presenting on SP1 at next month’s SoCal SharePoint Users Group, I hope to see you there.....

Standard Information:PSI Entry Point:

Project User: NT AUTHORITY\NETWORK SERVICE

Correlation Id: 865b6dd0-fe5d-4e08-968a-2abb1d5b7bab

PWA Site URL: http://trex-si-02/pwa

SSP Name: SharedServices1

PSError: Success (0)

Queue SQL connection is being retried. Error: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)

at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()

at System.Data.SqlClient.TdsParserStateObject.ReadByte()

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureNoResult(String storedProcedureName, SqlParameter[] parameters)

at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.GetJobCountPerfMon(String prefix, Int32& totalCount, Int32 idMarker, Int32& newJobCount, Int32& newIdMarker)

at Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.GetJobCountPerfMonSqlCall.Execute()

at Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.ExecuteRetryableSqlCall()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

That said, Thank You!!! SharePoint Products and Technologies Team in making a great product more better I feel that we are reaching a new milestone

-Ivan