Blogroll

Tuesday, May 15, 2012

SharePoint Redirect Web Part:


This can be accomplished using the java script on the SharePoint Site page. This script will prompts an end user that they will be redirected to another page after a certain period of time. .

1. First click Site Actions > Edit Page in the top right section of your browser window, where you wish to place the Redirect webpart.
2. Next you can add the Content Editor Web Part to a zone of your choice. Click on the Add a Web Part button ontop of the zone you chose.
3. This will bring up the Add a Web Part window. Scroll down to the Content Editor Web Part.
4. This will place the CEWP into the Top Zone or whichever zone you added it to. Clicking Edit > Modify Shared Web Part.
5. Once you have clicked the modify button a window opens on the right hand side of the browser with various options for the web part. You need to add your code the webpart so we will click the Source Editor… button.
6. Copy and paste the following code:

<'script type="text/javascript">
{
alert("This Site has been moved, please update your existing bookmarks. You will be re-directed momentarily");
}
<'/script>
<'meta http-equiv="refresh" content="15;url=http://yoursharepointURL.com/pages/default.aspx">


Into the Source Editor Windows that pops up when we clicked the Source Editor… button.
Note: Use the new SharePoint Site url where you want to redirect the users in the 'url=http://' (last line of the code snippet). 
7. Click the Save button, publish the page and your done. Users who access this page will be greeted with a popup and redirected in 10 seconds.
There are some drawbacks to this approach, and it's generally considered bad form to use a refresh tag to forward users. For one it breaks your users' Back button in their browsers. It can also confuse your users, especially if the redirect is fast and there isn't a note on the page explaining that the site has moved. Finally, make very sure the URL you're redirecting them to is valid. If not they get stuck on a dead page and no way to use Back to get out. Sometimes it is your only option though.
You can also choose to create a Redirect Page on the old site and use that as a redirect option, Unfortunately this solution only works on Publishing sites.

1. Go to your Pages document library and Click new.
2. Select Redirect Page, Provide a name in the title and click Ok.
3. Once the Redirect Page is created you'll need to Edit its Properties and enter the URL you want it to redirect to.
You'll also need to preview the page and check it in before it will work.

Complete detials on Plan external data conecction, security for Excel Services

CA was pointing to the different application server while opening from actual host of the CA.

Issue: CA was pointing to the different application server while opening from actual host of the CA. 

Steps taken to resolve the issue.   


-    We noticed that while opening the CA from server A, it was pointing to the server B.
-    On server A, we noticed that CA web app was pointing to the URL http://ServerB:8080. Clicking on the web application directly takes us to the http://ServerA:8080
-       We check the CA in IIS on the server Server B and it was not there as a result of un-provisioning it from the server, done last time. 
-       We agreed to un-provision and provision the CA on Server A using the command utility. 
-       We ran the command psconfig  –cmd adminvs –unprovision to un-provisioning the CA.   
-       We ran the command psconfig –cmd adminvs –provision port:8181 to provision the CA again. Both commands ran successfully. 
-       As a result we tried to open the CA from the Programs, it was now pointing to the URL http://ServerA:8181, which was expected result. 
-       We noticed in CA web application list, SharePoint Central web application was now also pointing to the URL http://ServerA:8181.

Removing Quick Launch Bar from SharePoint SItes.

Here are the steps to follow:

(1)Add content editor webpart on page
(2) Click on Modify shared webpart
(3) Click on source editor button
(4) Copy and paste the following HTML.

<'style>
.ms-quicklaunch
{
display:none;
}
.ms-navframe
{
display: none;
}
<'/style>

(5)Go to layouts section of that webpart and select Hidden

Removing/Adding a server to query role:

Removing a server out of query role:
- Stopped Office SharePoint Server Search from App server, it should take Problem server out of query role or Clicked on the service Office SharePoint Server Search from the problem server and remove the check box to take it out of the query role. 
- If Stopping it from CA result in error, Error from event logs. and follow the below steps
- Checked events logs and didn't find anything
- Pausing all active crawls from CA.
- Checked the service Process ID from TASKlist command by executing it from the farm admin account. 
- Kill the service from kill /f mssearch.exe.
- Checked from services.msc that Office SharePoint Sever Search is in disable state and from task manager.
- Deleted everything inside E:\index\'Guid ID for index folder' on the server to clear the space, which is having problem.
- Start the crawls.

Adding a server out of query role: 
-  "STOP Timer Scripts Service
- Once  timer service script is stopped. Proceed to add the server to query role.
- In the Service column, click Office SharePoint Server Search.
- On the Configure Office SharePoint Server Search Service Settings page, in the Query and Indexing section:
- Clear the Use this server for indexing content check box.
-Select the Use this server for serving search queries check box.
- Click Start. Then configuration of the application server as a query server is now completed.
- Confirmed from services.msc that service is in start state.
- Need to wait untill the index propegating gets finished if you have another query server in the farm. Watch SSP for the status.
- Once propagation finishes, restart timer services.
- Resume the stopped crawls.

ShareThis

snow flakes

blogger widgets Blogspot Tutorial

LinkWithin

Related Posts Plugin for WordPress, Blogger...