Skip to content


Add A Web Part To NewForm.aspx, EditForm.aspx And DispForm.aspx (Edit Page missing in menu)

I am in the process of creating custom forms for a list of mine, and here I needed to change some styling, and doing so is easy if you just add a Content Editor Web Part and add the style tag in there.

So off to the site actions menu I went to edit the page, only to find the menuitem missing.

So in order to edit the form pages, open up newform, editform or dispform depending which ones you want the webpart to be added to.

Add this like to the end of the url after the page has loaded.

&PageView=Shared&ToolPaneView=2

You can add the webpart now, and after it’s added the edit page menuitem is “back” again.

 

 

 

 

 

 

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in SharePoint.


Change from SharePoint Server name to Fully Qualified Domain Name (FQDN)

It is generally best practice to use fully qualified domain names when creating web applications in Windows SharePoint Services 3.0 and Microsoft Office SharePoint server 2007.
I am a bit excused in our environment since I was not hired when the servers and web applications were installed.

Prior to going Live with a SharePoint solution for our global company, the URLs would need to change from local server names to Fully Qualified Domain Names (FQDN). This is however not as much trouble as it seems.

Continued…

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in MOSS, SharePoint, WSS.


How to change Central Administration website URL – even after messing up AAM

I made a not so funny mess-up today. I changed the Alternate Access Mappings for my virtual machines Central Administration website, but I made a mistake in the url. Then when I wanted to change it back I couldn’t load up Central Admin.

I made the url mosstest.com but it should have been moss-test.com.

To fix it I could have just added mosstest.com in the hosts file under c:\windows\system32\drivers\etc\hosts but I wanted to figure out what else could be done.

Basically I found out that the Url for central admin can be sorted out by going to 2 places.

Continued…

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in MOSS, SharePoint, WSS.


Quick intro to creating custom SharePoint (MOSS, WSS) site themes

I will give a quick run through of how to create a site theme in Microsoft Office SharePoint 2007 and Windows SharePoint Services 3.0. Themes are a quick way to change the appearance of SharePoint. It is applied to each site (individually I’m afraid).
To me this is the easiest solution to creating the look you want. But this does not change layout. You will need to edit master pages and page templates for that.

Styling SharePoint is not hard, but it is very time consuming. For me it was also frustrating, so good luck :-) . Well I have not really touched styling before, so maybe that is why it was so time consuming for me.

Let’s get started.

Continued…

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in MOSS, SharePoint, WSS.


You do not have permissions to open this file on Excel Services.

After updating which URLs SharePoint could be accessed with, I was getting an error on some Business Data Catalog (BDC) dashboards.

I was getting this error:

You do not have permissions to open this file on Excel Services.  

Make sure that the file is in an Excel Services trusted location and that you have access to the file

What fixed it for me was:
1: Go to Central Administration and click on the link to SharedServices1 or whatever you named it.

2: Under Excel Services Settings click Excel Services Trusted File Locations

3: Edit each line to reflect what URL you access sharepoint with.
In my case I went from servername like:
“http://codejourney”
To a FQDN like:
“http://sharepoint.code-journey.com”
On the SharePoint site at work I made sure there was only one URL that would work for SharePoint, but if you got multiple paths to get to SharePoint you will probably need to have trusted file locations set up for each URL.
For instance, I could have had a trusted file location for both “http://codejourney” and “http://sharepoint.code-journey.com”.

This did it for me but if you are manually adding excel files or the likes to BDC you might need to add a new trusted file location altogether instead of editing existing ones.
You can do this by clicking “Add Trusted File Location” under Trusted File Locations.
Specify the share or address for the BDC files. This could be “http://sharepoint.code-journey.com/itmanager”.

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in MOSS, SharePoint Errors.


Enable Usage Analysis / Tracing / Reporting in SharePoint (MOSS)

 

Enable usage analysis / tracing in SharePoint
Sharepoint own “google analytics”.
Knowing what users look at what what they do not look at it important for any website owners.
This is true for sharepoint just as much as any other site.
Even if your sharepoint site is an intranet or extranet it’s important to know what the users DO on the site.
We have recently added a site where our different companies can purchase excess items from each others warehouses.
In these financial times trimming the stockpiles can be a wise decision.
What we want to know is how many actually look at each others stock. 
So basically we are looking at setting up usage analysis and tracing on our SharePoint extranet.
This will be done using the builtin “SharePoint Analytics” and then Google Analytics.
Google analytics can’t tell us which users visit the commodity exchange, but SharePoints own statistics will be useful for that.
This post will only discuss setting up “Usage Analysis Processing” in WSS and “Advanced Usage Analysis Processing” in MOSS, not the google analytics. I will discuss googles solution in a later post.
To enable Usage Analysis there are 3 steps:
1: Enable Usage Analysis Logging And Processing in WSS: 
Windows SharePoint Services Usage logging and Usage Analysis Processing must be enabled. 
When this is done, the actual logging starts. SharePoint will create folders in the 12\LOGS folder that is named by a GUID. The in that folder will be subfolders that contain logs for each day.
The logs don’t help you much unless you can look through them, and that is exactly what the Analysis Processing does. When the Processing is executed once per day, the logs will be parsed and the data will be added to the Content Database. From here reports will be made.
2: Enable Usage Reporting
There isn’t much in regards to Reports at this point. We are now using only the Windows SharePoint Services 3.0 reporting which is pretty minimal. The real reporting power lies in MOSS, so a farm administrator must go enable Usage Reporting in the SSP part of Central Administration.
These reports are much better, and supplements Google Analytics quite well.
3: Activate the Usage Reporting 
After the reporting has been enabled, the site collection administrators for each site collection must go activate the feature.
Only when the feature has been activated, the reports will be available for that site collection.
Enable Usage Analysis Logging And Processing in WSS:
1: Go to Central Administration and select the Operations tab
2: Under “Logging and Reporting”, Click the Usage Analysis Processing link.
3: In the Logging Settings part, Enable logging by clicking the checkbox.
4: If you don’t type in a log file location it will be using 12\LOGS per default. This will do just fine. If you change this, you will need to make sure the correct permissions are created for the folder. In 12\LOGS the permissions are already set up.
5: Under Processing Settings, click the checkbox and choose when to run the usage processing. The timeframe is when it should start processing. Choose to do it during the night.
 
Enable usage reporting:
1: Go to Central Administration and select the SharedServices1 (or whatever you called it) link.
2: Under Office SharePoint Usage Reporting, click the Usage Reporting Link.
3: Select Enable advanced usage analysis processing. This sounds like it will do the processing instead of WSS, but in fact it does not. It just adds on reporting functionality.
4: If you want to analyse search queries, select Enable search query logging. 
Activate the Usage Reporting:
1: Go to Site Actions -> Site Settings -> Modify all site settings -> Site collection features
2: Click Activate next to the feature called Reporting.
You are now able to look at those nifty reports. They are scattered all around.
There’s reports for sites, site collections and search.

Knowing what users look at and  what they do not look at is important for any website owners.

This is true for sharepoint just as much as any other site.

Even if your sharepoint site is an intranet or extranet it’s important to know what the users do on the site.

We have recently added a site where our different companies can purchase exces timber from each others warehouses.

In these financial times trimming the stockpiles can be a wise decision.

What we want to know is how many actually look at each others stock. 

So basically we are looking at setting up usage analysis and tracing on our SharePoint extranet.

This will be done using the builtin “SharePoint Analytics” and then Google Analytics.

Google analytics can’t tell us which users visit the commodity exchange, but SharePoints own statistics will be useful for that.

This post will only discuss setting up Usage Analysis Processing in WSS and Advanced Usage Analysis Processing in MOSS, not the google analytics. I will discuss googles solution in a later post.

Continued…

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in SharePoint.


Account failed to log on (0xc000006d) – Unable to load website from local server

Today I was changing which URLs were used for our company Intranet / Extranet.
What I changed was the “Alternate Access Mappings” and also bindings directly in IIS.

The reason for this was that I was setting up Google Analytics for SharePoint, and I did not want the internal employees to enter the MOSS site by simply using the SharePoint servers machine name (http://codejourney for instance).

After editing the Alternate Access Mappings and also bindings in IIS I noticed I was not able to enter the moss server using the new Fully Qualified Domain Name, FQDN (http://code-journey.com for instance).

Basically it did not work when logging on locally, but it worked when logging on remotely.

I also got the same error multiple times in the EventLog. One for each attempt to log in.

401.1 error. EventID 4625.

Error:

An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0×0

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: tsd
Account Domain: MyDomain

Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0×0

Process Information:
Caller Process ID: 0×0
Caller Process Name: -

Network Information:
Workstation Name: codejourney
Source Network Address: 10.1.1.185
Source Port: 57256

Detailed Authentication Information:
Logon Process:
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

 

Continued…

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in IIS, Windows Errors.


Clone SharePoint (MOSS / WSS) stand-alone developer virtual machine (Rename SharePoint Server)

I have often needed to copy a Windows SharePoint Services or Microsoft Office SharePoint Server developer Virtual machine.
I have gotten images from colleagues, or I needed to copy my own image.
I will assume your developer VM just uses the built-in SQL database (you installed SharePoint as standalone).
One company I worked for usually distributed Virtual Machines that did not have SharePoint installed on yet, but I would prefer just to have SharePoint installed and just rename the heck out of it.

The reason for this post is that, you can’t really just copy a VM and boot it up.
The SID and machine name of the virtual machine would be duplicate on the network and that is a bad idea.
This off course only happens if the copy and the original machine ever needs to be turned on at the same time.
If not then all these steps are not really needed and you can copy away.

Well basically what we need to do is rename the machine and also give it a new SID. Newsid.exe does both those steps.

Easy right? Well that is not all. SharePoint does NOT like it when you rename the machine, because of references that has been hardcoded into the system. You have to go through some steps before and after you do it.

I will go through these steps for you.

Continued…

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in SharePoint, Virtualization.


HRESULT: 0×80040E14 When Updating Or Uploading SharePoint Data

I have been posting a lot of errormessages recently. This day is no different. For some reason I am running into all kinds of errors in SharePoint and Windows. I must have terrible karma. I will hopefully get back to writing more general SharePoint or developer posts, once I got some more time. I got a SharePoint site going Live and it sure does give me a run for my money.

HRESULT: 0×80040E14 can show itself doing almost any operation that creates additional rows in any of the content databases.

The problem manifested itself when I was doing an Import of user profiles. It simply refused to import a few specific users.

The cause is your database server has run out of space. Go delete some files, and try your operation again.

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in SharePoint Errors.


Error when updating Windows SharePoint Services 3.0 with SP2 – An update conflict has occurred, and you must re-try this action. The object SPSearchDatabase…

Problem description:

I upgraded to SP2 on my dev machine, and test environment first, and it worked like a charm, so it was time to try it on the production server.
When I upgraded our production server with the SP2, I got an error when running the SharePoint Product and Technologies Configuration Wizard.
I got an error that there was an update conflict in a database caused by another service account already updating the database.

I got 3 Errors from upgrade.log:

1:

[SPManager] [ERROR] [9/9/2009 11:31:59 AM]: Upgrade [SPSearchDatabase Name=WSS_Search2_DKTAASR185 Parent=SPDatabaseServiceInstance] failed.
[SPManager] [ERROR] [9/9/2009 11:31:59 AM]: An update conflict has occurred, and you must re-try this action. The object SPSearchDatabase Name=WSS_Search2_DKTAASR185 Parent=SPDatabaseServiceInstance is being updated by DLH-GROUP\MOSS_FARM_Service, in the OWSTIMER process, on machine DKTAASR185.  View the tracing log for more information about the conflict.
[SPManager] [ERROR] [9/9/2009 11:31:59 AM]:    at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)

Continued…

  • Delicious
  • Digg
  • Twitter
  • Facebook
  • LinkedIn
  • TechNet
  • StumbleUpon
  • NewsVine
  • Technorati Favorites
  • Slashdot
  • MSDN
  • Share/Bookmark

Posted in SharePoint, SharePoint Errors.