It is known issues that on exporting list items, look up column
values are lost.
If the list is very big, it might not be possible to fix that
manually. This problem occurs since list template does look up on a table using
GUID, on creating a list template and exporting to a different site, this GUID
changes, hence it is no longer able to retain the values.
Suppose I have a list “Category” which has a look up column “sub
category” which refers to list “Sub Categories”. I assume you have already
created a look up list “Sub
Categories” in the destination web.
Browse to the source Web’s lookup list
“Sub Category” and choose Modify settings and columns.
Copy the source lookup list GUID from the
URL.It should be a sequence of numbers and letters similar to: %7BFFA47BF8%2D849C%2D4F20%2D9C50%2D173D2F5B6725%7D
Browse to the destination Web’s lookup
list and choose Modify settings and columns.
Copy the destination lookup list GUID
from the URL.Similar as point 2.
Delete %2D from the
string and replace with a dash sign (-). There should be no dash sign (-)
at the start and the end. GUID should be in the following format: FA47BF8-849C-4F20-9C50-173D2F5B6725
Save the source Web’s list that contains
a lookup column “Category” to the lookup list as a list template
called category.stp.
Export the list template STP from the
source list template gallery to the file system.
Rename the category.stp file to
category.cab so Windows can open it.
Open the file, right click on the
manifest.xml file and export it to the file system.
Edit the manifest.xml file; find the
source Web’s lookup list GUID and replace it with the destination Web’s lookup
list GUID.
Save the manifest.xml file.
Open a VS.NET command prompt.
Run the makecab command as: makecab
manifest.xml category.stp
Import the new STP into the destination
Web’s list template gallery. You will need to delete it if it has
previously been imported.
This documentation is to find or trace user activities on
SharePoint website
Purpose
When we enable Audit Logs in SharePoint, we can track all the
events related to additions and deletions of users/groups in SharePoint.
We can trace the same events using SQL queries queried on site
content database as a SharePoint Administrator in more detailed manner.
Steps for Auditing
Below are the queries which have been used to trace the user
deletions:
1.Get the group ID and Site ID from
below query
SELECT * from Groups with (nolock)
where Title=’GroupName’;
2.Get all deleted instances of that
particular site scope from the below query…
SELECT * from
AuditData with (nolock) where EventData like
'<roleid>-1</roleid><principalid>’Principal ID’</principalid>%'
and ItemType=6 and Event=’Event Id’;
3.Get the User details with the ID
‘Owner ID’ using the below query...
SELECT * from
UserInfo with (nolock) where tp_ID=’Owner ID’;
4.Get the permissions which are deleted
in the above Site Scope by USER from below Query…
SELECT * from
dbo.Perms with (nolock) where ScopeId=’Scope ID';
Restart Microsoft Internet
Information Services (IIS) 6.0. To do this, type the following line at the
command prompt, and then
press ENTER:
iisreset /noforce
Step2. Verify that the Administration Application
Pool Credential Deployment job definition is no longer displayed on the Timer
Job Definitions page of SharePoint 3.0 Central Administration. To do this,
follow these steps:
·Open SharePoint 3.0 Central Administration, click Operations, and
then click Timer job definitions under Global Configuration.
·Verify that the Administration Application Pool Credential Deployment
job definition is no longer displayed in the list.
Note: If the Administration Application Pool Credential Deployment
job definition is displayed in the list, wait until it disappears from the list
or delete after 10 minutes.
Step3.
Update the password for the application pool account that is used by Web
applications on the server farm. To do this, type the following line at a
command prompt on every server on the server farm, and then press ENTER: stsadm
-o updateaccountpassword -userlogin DomainName\UserName -password NewPassword
-noadmin
Step4. Update
the password for the account that is used to run the Windows SharePoint
Services Help Search service. To do this, type the following line at a command
prompt on every server on the server farm, and then press ENTER: stsadm.exe
-o spsearch -farmserviceaccount DomainName\UserName -farmservicepassword
NewPassword
Step5.
Update the password for the default content access account that is used by the
Windows SharePoint Services Help Search service. To do this, type the following
line at a command prompt on every server on the server farm, and then press
ENTER: stsadm.exe
-o spsearch -farmcontentaccessaccount DomainName\UserName
-farmcontentaccesspassword NewPassword
Step6.
Update the password for the account that is used by every Shared Services
Provider (SSP) on the server farm. To do this, type the following line at a
command prompt on every server on the server farm, and then press ENTER: stsadm.exe
-o editssp -title SharedServicesProviderName -ssplogin DomainName\UserName
-ssppassword NewPassword
Step7.
Update the password for the account that is used to run the Office SharePoint
Server Search service. To do this, type the following line at the command
prompt, and then press ENTER: stsadm.exe
-o osearch -farmserviceaccount DomainName\UserName -farmservicepassword
NewPassword
Step8.
If the server farm is configured to use single sign-on, update the password for
the account that is used by the Microsoft Single Sign-On Service. To do this,
follow these steps:
·Click Operations in SharePoint 3.0 Central Administration, and
then click Service accounts under Security Configuration.
·Under Windows service, click Single Sign-On Service.
·Under Configurable, specify the password, and then click OK.
Step9.
Update the password for the default content access account that is used by the
Office SharePoint Server Search service. To do this, follow these steps:
·Open SharePoint 3.0 Central Administration, and then click the link
to the SSP Web application under Shared Services Administration.
·Under Search, click Search settings, and then click Default content
access account.
·Specify the password to use for the content access account, and
then click OK.
Today we are going to talk about the Web services in
SharePoint. We all know SharePoint provide very extensive support for the web
services, writing custom web services, we will try to compile some information
on this.
What is a web Service?
A Web service
is a method of communication between two electronic devices over the Web
(Internet).
The W3C defines a "Web
service" as "a software system designed to support interoperable
machine-to-machine interaction over a network".
It has an interface described in a machine-processable format (specifically Web
Services Description Language, known by the acronym WSDL). Other systems interact
with the Web service in a manner prescribed by its description using SOAP messages,
typically conveyed using HTTP with an XMLserialization
in conjunction with other Web-related standards.
A web service
protocol stack is a protocol stack (a stack of computer networking protocols) that is used to define, locate,
implement, and make Web services interact with each other. A Web service
protocol stack typically stacks four protocols:
(Service) Transport Protocol: responsible for transporting messages between
network applications and includes protocols such as HTTP, SMTP, FTP, as well as the more recent Blocks Extensible
Exchange Protocol (BEEP).
(XML) Messaging Protocol: responsible for encoding messages in a common XML format so that
they can be understood at either end of a network connection. Currently,
this area includes such protocols as XML-RPC, WS-Addressing,
and SOAP.
(Service) Description Protocol: used for describing the public interface to a
specific Web service. The WSDL interface format is
typically used for this purpose.
(Service) Discovery Protocol: centralizes services into a common registry such
that network Web services can publish their location and description, and
makes it easy to discover what services are available on the network.
Web Services in
SharePoint?
The web service .asmx files are located at
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\ISAPI"
Every SharePoint Site has a virtual directory known as
"_vti_bin" which maps to the above directory. Don't believe
me? Open up your IIS management console, go to one of your web apps, and
look where "_vti_bin" maps to in the file system.
