SharePoint 2010 version mismatch after update

In some cases, after installing SP1 or hotfixes for WSS or MOSS, the version number reported in the site settings remains at the same version as before the upgrade.

There are several ways to verify if the upgrade was indeed succcesful

Check Versions table in the config and other content databases. If the table called Version

Check the Servers in Farm in Central Administration

Check the Site Settings for each Site collection

In the event some version number are not synchronized, try to run the following command

psconfig -cmd upgrade -inplace b2b -wait -force

In most cases, this should force version to be synced

Remove deleted WebPart from site galley

So you have a web part(s) in your site and you don't know how to remove. After searching up and down I found the solution under my nose.

If you check in SharePoint designer all files and navigate to _catalogs/wp.

Don't slap your head now.

Sharepoint Foundation 2010 New Web Application Prompting for Username and Password Credentials

Some interesting reading..

So I had a pretty stressful encounter with SharePoint security.

I got a error in Event log saying that I can't access the site with specified FQDN.
A bit of googling got me a answered.

SharePoint Foundation 2010 New Web Application Prompting for Username and Password Credentials.

Log Name:      System
Source:        LsaSrv
Date:          8.4.2012 11:53:53
Event ID:      6037
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:    xxxx
Description:
The program w3wp.exe, with the assigned process ID xxxx, could not authenticate locally by using the target name HTTP/xxx.xx.xx. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name.
 

You need to add the offensive FQDN to Lsa/MSV1_0.

1. Go to REGEDIT > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > LsaMSV1_0
2. Right click MSV1_0 > New > Multi-String Value
3. Type ‘BackConnectionHostNames’
4. Right click & select ‘Modify’
5. Enter the Hostname of the site: WEBSITENAME (and on a new line enter the FQDN, WEBSITENAME.domain.com as well)
6. Restart IIS

Source 

http://www.urtech.ca/2010/12/solved-sharepoint-foundation-2010-new-web-application-prompting-for-username-and-password-credentials/

and 

http://www.dotnetpulse.com/?p=70

Posted just for future reference.

SQL linked servers and Error[SQLSTATE 42000]

For successfully transfer data with a linked server you need to make the flowing changes on your servers.

On each server add a new Local or Domain user, use the same "username" and add it to run the SQL Agent service.
Grant permissions to this user on both databases.
On each server you need to run this command to make everything work


EXEC sp_addlinkedsrvlogin '<SERVERNAME>',
'true'

Use this comand to get the curently avalable servers.
exec sp_helpserver

Source Forum thread

Windows 7 change login background

Just for my or everyone else reference.

Follow the procedure below to change the Windows 7 logon screen.

1. Download the registry file from here. Extract the file and double-click on the file to enable this feature (Alternative method: right-click, select Merge).

2. Now, head over to the following folder:

C:\Windows\System32\oobe (“C” is your Windows Seven Installation drive)

3. Here, create a new folder named Info. Again, create a new folder inside the Info folder and rename it as backgrounds.

4. Copy your favorite image file to this folder and rename it as backgroundDefault. Note that the image must be in JPG format and the size should be less than 256 KB.

5. You are done. Reboot your system and see the change.

The following files (sorted by width-to-height ratio) are supported in  C:\Windows\System32\oobe\Info\Backgrounds folder:

* backgroundDefault.jpg

Source 

Pixel King TTL remote flash triger.

I ordered a Pixel TTL flash trigger system.
What I read this product is quite good and is comparable to Pocket Wizard.
I will post a full review when I have them.

http://www.pixelhk.com/Proshow.aspx?id=101

Change default color profile when using color management devices.

Hi.

I was frustrated by the quirk of color management on OSX. If you use a color calibration device then you can notice some diferences from application to application. The most reliable solution is to replace the "Factory Profile" with your "Curent Profile".

In the following image you can see the Factory Profile used by my HP Lp2475w HDMI connected display and my Curent Profile created with a HueyPro.

Before you dig into changing your system I should advise you that I don't hold any responsibility if you mangle your system beyond repair. 

If you wan't a consistent color management you have to replace the Factory Profile with a link to your Curent Profile. The easiest way is from Terminal.

Steps.
The paths and the names are only symbolic to show you the ColorSync matching to command line input.
1. Open terminal.
2. sudo -s, and type your password. You will drop to a root "supper admin" shel.
3. cd /System/Library/CoreServices/Resources/Profiles/ !! The path to "Factory Profile"
4. rm -f HD 709-A.icc !! Name of the currently used profile.
5. ln -s /Users/eriks/Library/ColorSync/Profiles/huey\ HpLIPHDMI.icc  HD\ 709-A.icc
6. exit

Thats it. Now you have a linked Factory Profile to your Curent Profile and when you recalibrate the settings are system wide.