Sunday, August 14, 2011

Access Denied in SharePoint Website

I don't know the reason for that problem and how it was happened.

The issue is that the webapplication is in locked mode

To solve this:

Central Administration -> Application Management -> Site Collection Quotas and Locks

Sunday, August 7, 2011

Unable to load assembly group - The user assembly group provider threw an exception

http://andreasglaser.net/post/2011/05/31/Sandboxed-solution-Unable-to-load-assembly-group-The-user-assembly-group-provider-threw-an-exception.aspx

While developing a sandboxed solution in SharePoint 2010 using the Visual Studio 2010 SharePoint developer tools it happened that I wasn’t able to deploy the solution using F5.

The error message wasn’t exact on how to solve the problem:

Error occurred in deployment step 'Add Solution': Unable to load assembly group. The user assembly group provider threw an exception while trying to provide user assemblies for the specified assembly group.

The detailed information about the error is the following:

Unable to load assembly group. The user assembly group provider threw an 
exception while trying to provide user assemblies for the specified assembly group. 
- Assembly group id: ", GroupId = "<SOME_ID>"" 
- Inner Exception: System.UnauthorizedAccessException: Access is denied. 
(Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))    
 at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(...)    
 at Microsoft.SharePoint.SPListCollection.EnsureListsData(...)    
 at Microsoft.SharePoint.SPListCollection.Undirty()    
 at Microsoft.SharePoint.SPBaseCollection.GetEnumerator()    
 at Microsoft.SharePoint.SPWeb.GetCatalog(SPListTemplateType typeCatalog)    
...

While doing a search I found a suggestion to change the account for the ‘SharePoint 2010 User Code Host’.
The developer image was set up by a colleague who didn’t use the farm account as the domain account for the SharePoint 2010 User Code Host service.

Here you can see the service... while trying to debug I realized that the given account on the right side was not the one I expected.

So I used the services under administrative tools and changed the domain account to the SharePoint 2010 farm account:

Changing the account solved my problem:

At the end I was able to deploy the sandboxed solution.

RSS Feeds using RSS WebPart

http://blog.mattsampson.net/index.php/2011/01/06/rss-feeds-using-rss-webpart?blog=1

RSS Feeds using RSS WebPart

Tech Stuff, Sharepoint (MOSS)

So you’ve got Sharepoint 2001 installed and you’ve got an RSS webpart on your page, but the error message says:
“The requested RSS feed could not be displayed. Please verify the settings and url for this feed. If this problem persists, please contact your administrator.”

What you may not know is that like your workstations and servers, if you use a proxy server then Sharepoint needs to also be configured to use it, as when a user goes to the page, it is the Sharepoint server that is requesting the RSS data and NOT the client’s IP address. Whereas this is quite useful from a firewall point of view as you can tie down the IP addresses which can access various things, it is a bit of a pain for the beginner admin user.
So what do you need to do?
You need to specify the proxy server in the Web.Config, using the System.Net element. Below are the steps in accomplishing that…
1. Open up the web.config file (eg: C:\inetpub\wwwroot\wss\VirtualDirectories\80)
2. Look for the xml node <system.net> (on line 669 for me)
3. There should be a <defaultProxy> xml node inside <system.net>. If you don't, create it.
4. There should be a <proxy> xml node inside <defaultProxy>. If you don't, create it.
5. If you have a autoDetect="True" attribute, remove it as it isn't needed if you are specifying a proxy.
6. Add the following attributes to the <proxy> xml node.
proxyaddress="http://proxy.company.com:8080"
bypassonlocal="true"
Your lines would like like this:
<system.net>
<defaultProxy>
<proxy proxyaddress="http://10.28.1.253:3128" bypassonlocal="true" />
</defaultProxy>
</system.net>
7. Save the web.config.
8. Go to the Command Line (CMD) and type: iisreset
9. You are ready to go.
If you have an authenticated RSS feed, then you would need to work with Kerberos authentication, which is a whole new ball game!
A Good RSS feed to test with is one of the BBC news feeds:
BBC News for England - http://feeds.bbci.co.uk/news/england/rss.xml
BBC Sports News - http://newsrss.bbc.co.uk/rss/sportonline_uk_edition/front_page/rss.xml
(Thanks to Technet and Kit Kai’s Tech Blog for help with this - http://community.sgdotnet.org/blogs/kitkai/archive/2007/04/04/Consuming-RSS-Feeds-using-RSS-WebPart-.aspx)

Thursday, July 28, 2011

Error message when you open a Web site by using Basic authentication in Expression Web on a computer that is running Windows Vista: “The folder name is not valid”

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

Error message when you open a Web site by using Basic authentication in Expression Web on a computer that is running Windows Vista: “The folder name is not valid”

View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 (http://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows registry

Expand all | Collapse all

SYMPTOMS
When you open a Web site by using Basic authentication in Microsoft Expression W...

When you open a Web site by using Basic authentication in Microsoft Expression Web on a computer that is running Windows Vista, you may receive the following error message.

The folder name is not valid.

Back to the top

WORKAROUND
Warning Serious problems might occur if you modify the registry incorrectly by u...

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this issue, follow these steps:

Click Start, type regedit in the Start Search box, and then click regedit in the Programs list.
Locate and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Point to New, and then click DWORD (32-bit) Value.
In the right pane, type BasicAuthLevel to name the new registry entry, and then press ENTER.
On the Edit menu, click Modify.
In the Value data box, type 2, and then click OK.

Note The mapping is as follows:
- 0 - Basic authentication disabled
- 1 - Basic authentication enabled for Secure Sockets Layer (SSL) shares only
- 2 or greater - Basic authentication enabled for SSL shares and for non-SSL shares
Restart the computer.

Back to the top

MORE INFORMATION
Basic authentication is one form of user authentication where a user is identifi...

Basic authentication is one form of user authentication where a user is identified to the server.

When the server is configured to use Basic authentication, the client computer transmits the users' credentials to the server. If the channel is not encrypted, such as in typical HTTP traffic, a malicious user on another computer on the network can possibly intercept the user name and the password of that user.

By default, Basic authentication is disabled in Windows Vista. When Basic authentication is disabled, either the client computer uses a different authentication method (if the server supports a different authentication method), or the request fails.

Wednesday, June 8, 2011

User profiles Sync DB doesn't have Tables or Stored Procedures

Issue:

While you are trying to import the user profiles in SharePoint 2010, you will get lots of errors. Particularly, we will face some of the issues like below:

1. Forefront Identity Manager Service may not be started.

2. Forefront Identity Manager Synchronization service may not be started.

3. If you see the "eventvwr", you will get some of the errors like below:

Error 1:

The Forefront Identity Manager Service cannot connect to the SQL Database Server.

The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.

Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.

Error 2:

.Net SqlClient Data Provider: System.Data.SqlClient.SqlException: Could not find stored procedure 'RegisterService'.

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

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

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.ResourceManagement.Data.DataAccess.RegisterService(String hostName)

Error 3:

The Forefront Identity Manager Service was not able to initialize a timer necessary for supporting the execution of workflows.The Forefront Identity Manager Service could not bind to its endpoints. This failure prevents clients from communicating with the Web services.

Error 4:

A most likely cause for the failure is another service, possibly another instance of Forefront Identity Manager Service, has already bound to the endpoint. Another, less likely cause, is that the account under which the service runs does not have permission to bind to endpoints.

Ensure that no other processes have bound to that endpoint and that the service account has permission to bind endpoints. Further, check the application configuration file to ensure the Forefront Identity Manager Service is binding to the correct endpoints.

Solution:

I have spent lots of time to fix this issue. Hmmmm... The solution is in SQL server side. In SQL Server database, you cannot find any "tables" or "Stored Procedures" in "Sync DB"

I have given the solution in single screenshot. In the below screenshot, set the "db_owner" schema for "dbo".

If you set the "dbo" as "db_owner", you can able to start the "Forefront Identity Manager Service". so that you will be able to start the profile import process.