Installing SharePoint 2010

This was no easy task my friends. There are several pre-requisites prior to actually running the beta installer. This person did a fine job of listing them all out and it what helped me through installation.

http://blogs.msdn.com/opal/archive/2009/10/25/sharepoint-2010-pre-requisites-download-links.aspx

A few points to highlight from a 2007 installation to 2010

• Windows Server 2008
• 64x OS
• SQL server 2008
• Building the SQL server was a bit frustrating for me as there were several service packs and CU updates needed - pay close attention when installing SQL or else your install will fail.

Free SharePoint Performance Monitor - Idera

Anyone who is on a budget might appreciate this by Idera.

SQL Error 18456, Severity: 14, State: 16 - Login Failed

Yippppie another awesome error - solution coming soon. Let the count down begin... (really this one only took a few hours, it was an easy one..compared to most)

OK so that was extra stupid. All regarding this SharePoint SSP SQL job; 'DBName_DB_Job_DeleteExpiredSessions'. In my case the job is named 'SharedServices_DB_Job_DeleteExpiredSessions' and I don't even have a database named that. My SSP db is called...'SSP_DB' so I modified steps inside the job by using properties and clicked on steps. The database drop down was set to null, which is why (I think) I was getting errors on 'Master' So I just changed the association to the correct db and it works great now.

I finally found this TechNet blog post explaining what this dang job does...for your reading pleasure. This post also assisted in solving this mystery.

I just want to note that I also have more than one of these jobs, which is due to multiple SSP restores. I also had to kill those by just right clicking on the job and choosing disable. After refreshing the application log in the Event Viewer on the SQL server all my lovely errors are gone.

Excel file opening in Excel Services

Normally this would be a good thing, however the file being accessed is not an Excel Services file. What's worse is I can't recreate the issue and every other user I've asked to open the file can't either. Screen shots from the problem user though are clearly trying to open in Excel Services and giving a access denied error.

SharePoint only frustrates me when stuff like this happens. When stuff affects one user, it's a life or death issue to the one user so I have to spend time researching it and trying to recreate it. I admit I'm stuck, I have no fix except for a direct link to the file. Explain that one...

Kindly reply to this post if you think you know what's going on.

SharePoint ULS logs - Tracing service lost trace events

Another bug - go figure.

Deployed workflow last night, didn't go, went to check ULS logs and guess what.

08/12/2009 13:45:51.90 wsstracing.exe (0x0758) 0x127C ULS Logging Unified Logging Service uls1 Monitorable Tracing Service lost trace events. Current value 4.


Log files are filled with errors. Tried to stop the service and it's hung on a "stopping" state, tried to kill the process via task manager and got nothing. Last line of action is to reboot the server, will try tonight after hours.

Here are Microsoft's Workarounds: https://connect.microsoft.com/feedback/Workaround.aspx?FeedbackID=408671&SiteID=428

SharePoint Meta Data doesnt transfer with a "COPY"

I'm in the middle of redoing some file organization and came to the realization that the "COPY" function does not keep associated meta data and content types. You must use "CUT" if you want this data to transfer with the files.

The issue is that when doing this with Windows Explorer is it might or might not work with CUT - most folders error out with a file name being too long.

The solution is to use the "Manage content and structure" feature - well that doesnt work for me.

I haven't tested with RoboCopy, but will soon and hope to use the CUT command as I have several thousand files and folder to move and delete.

SharePoint Designer Workflow Error

Another lame error from Microsoft, forgive me for naming my task the same as my workflow...go figure.

"You specified identical destination filenames for some of the files you are trying to copy. Make sure all destination files have unique names and try again."

This message appears when you attempt to compile a workflow that:
Is set to start manually.
Includes a task action where the name of the task is identical to the name of the workflow.

Cause
When you compile a workflow, Office SharePoint Designer 2007 saves the initiation form (Workflow_name.aspx) and the custom task form (Task_name.aspx) to the same workflow folder. A workflow will not compile successfully if these forms have the same file name because two files in the same folder cannot have the same file name.

Resolution
Rename the task in the workflow:
In the task action, click the link that opens the Custom Task Wizard.
Click OK in the warning message about how changing the custom task may break running instances