which country user step here?

Tag Cloud

MOSS (47) SharePoint 2007 (37) SharePoint 2013 (25) SharePoint 2010 (22) MOSS admin (17) PowerShell (17) admin (17) developer (16) List (15) WSS (14) sql query (14) MOSS SP2 (13) end user (11) scripting (11) wss V3 (11) Moss issue (8) search (8) permission (7) sql (7) Service Pack (6) database (6) reportadmin (6) workflow (6) Excel (5) RBS (5) client object model (5) CU (4) Client Code (4) Command (4) Cumulative Updates (4) IIS (4) Patch (4) SharePoint designer (4) stsadm (4) ASP.NET (3) Content Database (3) Groove (3) Host Named Site Collections (HNSC) (3) Tutorial (3) alert (3) batch file (3) codeplex (3) error (3) incomming email (3) restore (3) upload (3) user porfile (3) Caching (2) Folder (2) Index (2) Internet (2) My Site Cleanup Job (2) My Sites (2) News (2) People Picker (2) Share Document (2) View (2) Web Development with ASP.NET (2) add user (2) authentication (2) coding (2) column (2) deploy solution (2) domain (2) download (2) enumsites (2) exam (2) export (2) issue (2) june CU (2) load balance (2) mySites (2) network (2) office 365 (2) orphan site (2) performance (2) profile (2) project server (2) query (2) server admin (2) theme (2) timer job (2) training (2) web master (2) web.config (2) wsp (2) 70-346 (1) 70-630 (1) AAM (1) Anonymous (1) Approval (1) Cerificate (1) Consultants (1) Content Deployment (1) Content Type (1) DOS (1) Document Library (1) Drive Sapce (1) Excel Services (1) Export to Excel (1) Feature (1) GAC (1) Get-SPContentDatabase (1) Get-WmiObject (1) HTML calculated column (1) ISA2006 (1) IT Knowledge (1) ITIL (1) Install (1) Link (1) MCTS (1) Macro (1) Migration (1) NLBS (1) Nintex (1) Office (1) Open with Explorer (1) ROIScan.vbs (1) Reporting Services (1) SPDisposeCheck.exe (1) SQL Instance name (1) SSRS (1) SharePoint admin (1) SharePoint farm (1) Shared Services Administration (1) Site Collection Owner (1) Site template (1) Steelhead (1) URLSCAN (1) VLOOKUP (1) WSS SP2 (1) XCOPY (1) abnormal incident (1) admi (1) app (1) application pool (1) aspx (1) audit (1) availabilty (1) backup (1) binding (1) blob (1) branding sharepoint (1) cache (1) calendar (1) connection (1) copy file (1) counter (1) crawl (1) custom list (1) event (1) excel 2013 (1) facebook (1) filter (1) fun (1) group (1) iis log (1) import (1) import list (1) improment (1) interview (1) keberos (1) log in (1) metada (1) migrate (1) mossrap (1) onedrive for business (1) operation (1) process (1) publishing feature (1) resource (1) security (1) send email (1) size (1) sps2003 (1) sql201 (1) sql2012 (1) sub sites (1) system (1) table (1) task list (1) today date (1) vbs (1) video (1) web part (1) web server (1) widget (1) windows 2008 (1) windows 2012 R2 (1) windows Azura (1) windows account (1) windows2012 (1) wmi (1)

Monday, December 21, 2015

SharePoint Incoming email basic checking

Issues : user unable to send mail to the SharePoint document library  ( setup is done, is suddenly out of service )

checking step  :
  • To confirm is the SharePoint timer service problem or  other issues, i have tested to send the email to other document library with email incoming enable. Is working , so we narrow down is not the SharePoint timer service issues.
  • secondly need to check and see the email have send out from email server to our server or not , this can go to each web front end sever drive D:\inetpub\mailroot\Drop , you will see some item there. You can use notepad to open the xxx.eml item then you will see the sender from and to also other email detail . then this is confirm not email server issues.
resolution step :
  • disable the incoming email and the document library then wait for few minute and enable it back.

Wednesday, December 16, 2015

Host Named Site Collections (HNSC)

刚刚学到新的SharePoint 2010 / 2013 的新知识,就是 Host Named Site Collections (HNSC) . 很少公司会用这种方法,普通用法都是 path-based site collections 然后和 host headers 而已。

Example path-based site collections :
 Team A has a site collection http://contoso.com/sites/teamA
 Team B has a site collection  http://contoso.com/sites/teamB

Host named site collections :

Use host headers and host-named site collections

Host headers allows the web server to host multiple web sites on the same IP Address and Port combination. If the incoming HTTP request includes a host header name, and a matching host header is configured in IIS, IIS will respond with the content from the appropriate web site.
Host headers are configured at the Web Application (IIS website) level, they are one of the website bindings properties.
It is important to understand the distinction between Host headers in IIS and Host Named Site Collections. Host headers at the IIS website level are only intended for path-based site collections.
When using Host named site collections, SharePoint is responsible for resolving the correct site for the address based upon the incoming request passed through IIS. In most cases, applying a host header binding at the IIS website level makes it impossible to access host-named site collections through the IIS website. This is because IIS will not respond to requests for host names that differ from the host header binding.
If an existing web application has a host header binding set, IIS will not return pages from the host-named site collection until you remove the binding from IIS. For more information, see Update a Web application URL and IIS bindings (Office SharePoint Server 2007).

Mix host-named site collections and path-based site collections in the same web application

You can use host-named and path based site collections in the same web application. To ensure that both types of site collections are accessible to users, do not put host header bindings on the IIS website of your web application, including IIS websites for zones that are extended from the web application. If an existing web application has a host header binding set, IIS will not return pages from the host-named site collection until you remove the binding from IIS.


Sunday, December 6, 2015

Excel 2013 - Getting challenged for username and password

Error message : "A connection to the SharePoint site cannot be established.  To synchronize or refresh your table, you must be able to connect to the SharePoint site"

Background story :

We are using SharePoint 2010 and have several Excel spreadsheets that have data connections in them that use a SharePoint list to refresh data (not using excel services).  The Excel spreadsheets are stored in a SharePoint document library and the site is a trusted location.  All of our users have at least read access to the library as well as the SharePoint lists where the data is stored.  Some of the lists are coming from a site that is in a different site collection than where the Excel spreadsheet is stored.
Our problem is this:  Our users that are running Excel 2010 can open and refresh the data just fine.  Our users running Excel 2013 are constantly challenged for user name and password (it does not accept it when it is entered) and the data does not refresh.  The error message is "A connection to the SharePoint site cannot be established.  To synchronize or refresh your table, you must be able to connect to the SharePoint site".    Then it tells you which data range failed to refresh.  When you click OK, it goes on to the next connection that it cannot connect to and repeats the process until you have gone through all of the connections.
No permissions have been changed and these users could access the spreadsheet before being upgraded to Office 2013.  They are using Windows 7, Service Pack 1.  I am the farm administrator and am able to open the spreadsheet in Excel 2013.  I've tried increasing the user's permissions but it still won't open for them.

Solution :

Grant the permission to user/group to the SitePages Document Library

URL Discussion :