One or more field types are not installed properly. Go to the list settings page to delete these field" exception.

Thread from: http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/a2c6bed0-eee1-4f9b-b468-fc57c2e45c16


<Where>
<And>
<Eq>...</Eq>
</And>
</Where>

This will throw the "One or more field types are not installed properly. Go to the list settings page to delete these field" exception.

Good code:

<Where>
<And>
<Eq>...</Eq>
<Eq>...</Eq>
</And>
</Where>

or

<Where>
<Eq>...</Eq>
</Where>

BizTalk: Failed to update binding information

Post from: http://felixmondelo.blogspot.com/2008/05/deploy-orchestrations-failed-to-update.html

Receive Location '' has no Transport type specified.

BizTalk stores info about the last deployments in:

C:\Documents and Settings\[user name]\Application Data\Microsoft\BizTalk Server\Deployment\BindingFiles

Windows 7

C:\Users\[user name]\AppData\Roaming\Microsoft\BizTalk Server\Deployment\BindingFiles

When you do a redeployment, BizTalk uses this information. If this information is with errors, we get this error "Failed to update binding information".

Solution is to remove the info binding file.

An invalid parameter or option was specified for procedure 'sys.sp_change_users_login'

Msg 15600, Level 15, State 1, Procedure sp_change_users_login, Line 214

An invalid parameter or option was specified for procedure 'sys.sp_change_users_login'.

I ran this script:

EXECUTE sp_change_users_login @action = 'auto_fix', @UserNamePattern = 'login'

Fix:

I added @Password parameter:

EXECUTE sp_change_users_login @action = 'auto_fix', @UserNamePattern = 'login', @Password = 'password'

SharePoint disable loopback check

Post from: http://www.jeremytaylor.net/2010/05/24/sharepoint-disable-loopback-check-disableloopbackcheck-dword-in-registry/

I was constantly prompted for the username and password. In SharePoint 2010, it can really annoy you by not accepting your username password credentials in the popup window.

Its a ‘feature’ on the server that you need to disable as a workaround.
Caution: Microsoft Best practices is out of scope in this article. Do your own research on this topic.

You would need to create a DWORD registry key in the registry called DisableLoopbackCheck and set it to 1.
Follow these steps:

Click Start, click Run

Type regedit, and then click OK
In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value. (In Win 2008, its DWORD 32bit)
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1 and then click OK.
Quit Registry Editor.
You may need to restart your server.

For more information about this, click the following article number to view the article in the Microsoft Knowledge Base: 281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name.

The type was not expected. Use the XmlInclude or SoapInclude attribute to specify types that are not known statically.

Post from: http://www.johnsoer.com/blog/?p=125&cpage=1#comment-5494

1. public class Test
2. {
3. private string _Field = "";
4. public string Field
5. {
6. get { return _Field; }
7. set { _Field = value; }
8. }
9. }
11. public class TestInherited : Test
12. {
13. }
15. public class Container
16. {
17. private Test ivField;
18. public Test Field
19. {
20. get { return _Field; }
21. set { _Field = value; }
22. }
23. }
25. Container _Test = new Container();
26. _Test.Field = new TestInherited();

Solution:

new XmlSerializer(typeof(Container), new Type[] { typeof(TestInherited) });

This solution was not working for me because:

There was a namspace on my XmlRoot element [XmlRoot("Container", Namespace = "http://namespace", IsNullable = false)]

When i removed namespase, the problem was gone.

Hope this helps someone.

Setup WRT54G (or similar) running DD-WRT as Access Point

Blog from: http://www.maximumpc.com/forums/viewtopic.php?t=59541

Setup > Basic Setup > WAN Connection Type: Connection type: Automatic Configuration - DHCP

Enter a good (outside of your DHCP range) IP address (and, of course, match your current subnet);

Setup > Basic Setup > Network Address Server Settings (DHCP): DHCP Server: Disable
Setup > Advanced Routing > Operating Mode: Operating Mode: Router

Setup > Advanced Routing > Dynamic Routing: Interface: Both

Setup > Advanced Routing > Static Routing: Interface: LAN & WLAN

SSRS 2008 R2 and UAC problem

Post from: http://calebs71.blogspot.com/2010/09/ssrs-2008-domain-user-issue.html

Scenario: I have a new SQL Server Reporting Services 2008 R2 x64 instance that works if you are the local administrator. Once I switch to another user who is an implied administrator via an AD group I get the following error when attempting to access SSRS in a browser:

"User 'TESTDOM\user' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed."

The user is a member of the domain admins group which is obviously a member of the local admins. Also if I right click on IE8 and say "Run As Administrator" it works. The quick fix is to disable the UAC. If you don't want to do that then just do the below:

1. Launch IE8 using "Run As Administrator" and in SSRS (http://servername/Reports) click on Site Settings. In Site Settings navigate to "Security" and add your user "TESTDOM\user" as a System Administrator.

2. Click on "Home" and then "Folder Settings". Now add your account again this time assigning yourself all the roles (Browser, Content Manager, My Reports, Publisher, Report Builder).

3. Close Administrative IE session and open a normal IE8 window and your SSRS should work.

Fix SharePoint 2010 alert url's

http://technet.microsoft.com/en-us/library/cc508847.aspx

Login failed for user .

Server Name: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Error Number: 18456

Severity: 14

State: 1

Run SSMS as Administrator.

Could not create SSOSQL. Error Code: 0x80131700

This is for x64 OS:

"C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\win32\ssosql.dll"

"C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\win32\ssosql.dll"

"C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll"

"C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe" "C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll"

Restoring SQL Server 2005 Suspect Database

Post from: http://mshehadeh.blogspot.com/2007/09/restoring-sql-server-2005-suspect.html

EXEC sp_resetstatus 'DBname'

ALTER DATABASE "DBname" SET EMERGENCY

DBCC checkdb('DBname')

ALTER DATABASE "DBname" SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB ('DBname', REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE "DBname" SET MULTI_USER

The SSO service failed to start. After installing VS 2010

Post from: http://blogs.msdn.com/ashishme/archive/2009/08/14/fixing-biztalk-entsso-failure-on-windows-7-vista-or-server-2008-after-vs-2010-beta-installation.aspx\

I've been running BizTalk 2009 on my Windows 7 machine, and after installing VS 2010 beta 2, the Enterprise Single Sign-On Service stopped working.

It failed with the following error:

Could not create SSOSQL. To fix the problem, reinstall SSO or try 'regasm SSOSQL.dll' from a Visual Studio command prompt.
Error Code: 0x80131700

The file is located at C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll

Run Visual Studio Commmand prompt as Administrator and run 'regasm "C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll"'.

On 64 bit machines (windows 7, Vista, W2008 etc) you need to call regasm.exe utility explicitly from this folder:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered error with 64bit OS

Post from: http://weblogs.asp.net/cazzu/archive/2007/11/16/the-microsoft-ace-oledb-12-0-provider-is-not-registered-error-with-vista-64bit.aspx

If you're getting this error while trying to connect to Access 2007 or Excel 2007 via the Office 12 OleDB provider, you must first make sure you have the Office 2007 data providers installed.

Next, under x64 (64bit), the data providers will not work by default as they are 32-bit only (x86), even if the data providers download page doesn't say it. You have to explicitly compile for x86 instead of the default "Any CPU" platform:...

Read full article

The description for Event ID ( 17137 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found

Post from: http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sharepoint.setup_and_administration&tid=71af2356-f92e-4b15-8b09-798a91288cc3&cat=〈=&cr=&sloc=&p=1

Solution:

Open SQL server management studio.

Right click the database and select Properties->Options.
See if Auto close is set to True. If it is true, set it to false.

The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired

http://support.microsoft.com/kb/971620

No exact match was found domain users. Domain users

Post from: http://weblogs.asp.net/erobillard/archive/2007/07/06/how-to-change-service-accounts-and-their-passwords-in-moss-and-wss-3-0.aspx

Change the Application Pool Identity for SharePoint Central Administration (SCA)

Repeat these steps on each server which hosts the SharePoint Central Administration web application. If the web front-end (WFE) and application (APP) server roles are served by separate machines, SCA should be enabled on one APP server (or more) and stopped and/or removed from the WFE servers. This allows control over access to the SCA. The SCA service account should not be the same as that used for the SharePoint application pool so even if one is compromised, the other remains secure.

1. Open a command prompt.
2. Run: stsadm -o updatefarmcredentials -userlogin domain\username -password password
3. Be patient. This may take a few minutes to run.
4. To restart the application pool, either open IIS and recycle the application pool, or open a command prompt and type iisreset -noforce
5. Open SharePoint Central Administration in a browser to confirm that the change was successful.

The above steps create an Administration Application Pool Credential Deployment timer job. You can see this in the Timer Job Definitions page. The job is complete when it no longer appears in the list of definitions (refresh the browser, this isn't automatic).

Cannot connect to the configuration database. Event ID: 33002

Post from: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/8b3094a1-31ee-49d7-ab02-72ca0dc440a7

Description:
The description for Event ID ( 33002 ) in Source ( MSSQL$MICROSOFT##SSEE ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: module, dbo.proc_getObjectsByClass.

Solution:

Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.

Important Because of a problem with the hotfix installation, you must not run the SharePoint Products and Technologies Configuration Wizard to complete the installation if you are running a Windows SharePoint Services stand-alone installation that uses the Windows Internal Database Engine. Instead, you must use the Psconfig.exe command-line utility. To do this, follow these steps:

1.	Click Start, click Run, type cmd in the Open box, and then click OK.
2.	Change to the following directory: system drive\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin
3.	Run the following command: psconfig -cmd upgrade -inplace b2b

If you ran the SharePoint Products and Technologies Configuration Wizard, you may experience a long delay, and the wizard may not be completed successfully.

Alternatively, the configuration process may be unsuccessful, and you may receive the following error messages:

Configuration Failed

An exception of type System.Data.SQLClient.SQLException was thrown. Additional exception information access to module dbo.proc_MSS_GetConfigurationProperty is blocked because the signature is not valid.

Additionally, the following event may be logged in the Application log:

Event ID: 5586
Source: Windows SharePoint Services 3
Unknown SQL Exception 33002 occured.
Additional error information from SQL Server is included below.
Access to module dbo.proc_MSS_GetConfigurationProperty is blocked because the signature is not valid.

If you experience these issues, use the Psconfig.exe command to manually complete the installation of the hotfix.

If this doesn't help try this:

Superb, worked great. Found that the search service was disabled so it failed, but I had to run the command line again with -force on the end after setting the service to automatic.

Thanks very much for your help.

- Kurt

BizTalk Error: Project Creation Failed

Post from: http://blogs.msdn.com/kerreybpi/archive/2009/05/12/biztalk-error-project-creation-failed.aspx

SYMPTOMS

The error message appears on the status bar when you try to add a BizTalk 2009 project in Visual Studio 2008.
-----------------------------------------
Error Details: “Create BizTalk Project …. Project Creation Failed”

This problem may occur after you applied SP1 for VS.

RESOLUTION

Browse to the installation folder of BizTalk 2009, run setup.exe, and choose “Repair” button, after that, you will work out the issue.

Error when using Upload File or New Data Source option in Report Manager

Post from: http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/af7650a8-148c-455e-99f3-3384b073e66f/

Problem:

I have just installed SQL Server 2008 and am having problems using Report Manager. Initially, I had problems accessing Report Manager so I removed the SSL identifies on both the web service and report manager website using the configuration manager.

This solved the problem of accessing Report Manager. However, if I now click on either the "Upload File" or "New Data Source" buttons in Report Manager I get the following error:

"Internet explorer cannot display the webpage".

Resolution:

Go to: C:\Program Files\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\ReportServer

Open: rsreportserver.config

Set value of "SecureConnectionLevel" to 0 (zero);

Restart your Report Server.

Rebuild master DB SQL Server 2008

1. From a command prompt window change to the following directory:

"C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release"

2. Next paste the following into the command prompt window and press “Enter”:

Setup.Exe /Action=RebuildDatabase /InstanceName=MSSQLSERVER /SqlSysAdminAccounts=Admin /Quiet

If you have SQL configured for Mixed Authentication Mode use the same syntax except you must also provide the /SAPWD parameter to specify the SA password. If you don't, you will get an error.