I moved my blog to a new domain.
Please visit
Thanks.
In order to solve this issue,
1) Go to Central Administration >Application Management >Manage service applications >Visio Graphics Service >Global Settings
2) Check the Application ID under Unattended Service Account, if noting there, you need to create one. In order to create one, follow the steps listed below.
Follow the following steps in order to create a new secure store target application:
Go to Central Administration | Application Management | Manage service applications | Secure Store Service
Go to visio graphics services settings and enter the application ID, you just created.
Go to central admin and reanalyze the error message. This will take care of this error.
Thanks
Using highly-privileged accounts as application pool or as service identities poses a security risk to the farm, and could allow malicious code to execute. The following services are currently running as accounts in the machine Administrators group: SharePoint – 100 (Application Pool)
SharePoint – 107 (Application Pool)
SharePoint – 197 (Application Pool)
SharePoint Central Administration v4 (Application Pool)
FIMSynchronizationService(Windows Service)
OSearch14(Windows Service)
SPTimerV4(Windows Service)
WebAnalyticsService(Windows Service)
Browse to http://…your server Name…/_admin/FarmCredentialManagement.aspx
and change the account used for the services listed in the explanation. For more information about this rule, see “http://go.microsoft.com/fwlink/?LinkID=163445”.
Failing Services SPTimerService (SPTimerV4)
TO SOLVE THIS ISSUE:
Create different service accounts to run different services as listed below.
you can also
http://technet.microsoft.com/en-gb/library/hh344223.aspx
or for more details, visit
http://smallcitydesign.com/accounts-used-by-application-pools/
Changing from express to enterprise version in SQL database
You can back up the SharePoint databases and restore them to new enterprise SQL server by using detach method. Please follow the following procedure.
To Restore the DB into SQL
2. Open up Central Admin
3. Create/Extend Web Application
4. Create a new web application
5. Enter everything as normal, however when you get to the database, put in the DB name of the database you restored into SQL. SharePoint won’t complain that it already exists, rather it will just use that database, including all the content in it, to create the web application.
If you will reinstall SharePoint to the farm installation, you will be prompted to enter a SQL server name and credentials. After you will configure your SharePoint you can re-create web applications and site collections. If you will use the existing database names, SharePoint will just attach the content databases instead of creating new ones. You have to install RBS on your Enterprise server, or you have to migrate the content from RBS back to your content database and later reconfigure SP to use RBS on your Enterprise server.
In a case you will at first migrate your RBS back to content DBs you can safely detach the database on your SQL and attach to your Enterprise SQL system.
Please read the link below to Migrate content into or out of RBS (SharePoint Foundation 2010)
http://technet.microsoft.com/en-us/library/ff628255.aspx
Hope this helps. Please let me know, thanks
Microsoft Office SharePoint Server (MOSS) for Developers
Introduction
Microsoft ASP.NET 2.0 provides a Web Part infrastructure that helps you build custom Web Parts and deploy them to Web sites built using Microsoft Windows SharePoint Services 3.0.
This article provides recommendations for best practices to choose between ASP.NET 2.0 Web Parts and Windows SharePoint Services 3.0 Web Parts according to business needs, reviews ASP.NET 2.0 Web Part infrastructure, and walks you through how to build custom Web Parts that work in both standard ASP.NET 2.0 Web sites and Windows SharePoint Services 3.0. The article also outlines deployment and security considerations to address before adding Web Parts to SharePoint sites.
You will need to install the Windows SharePoint Services 3.0 SDK
Web Part Frameworks
SharePoint Web Parts are UI elements that support both customization and personalization. A Web Part is an ASP.NET server control designed to be edited and modified by knowledge workers in the browser. It works as a component of a SharePoint site that presents information pulled from multiple data sources. With Web Parts, you can create information dashboards on corporate portals and Web sites. Web Part pages allow you to personalize information relevant to your needs by updating the value of specific Web Part properties.
The Web Part infrastructure in Microsoft Windows SharePoint Services 2.0 and Microsoft Office SharePoint Portal Server 2003 allowed you to build custom Web Parts targeted to Microsoft SharePoint Products and Technologies by using managed code.
ASP.NET 2.0 includes a new Web Part control set that allows site customization and personalization on custom Web sites that are independent of SharePoint Products and Technologies.
The Web Part infrastructure in Windows SharePoint Services 3.0 exists on a layer above the ASP.NET 2.0 Web Part infrastructure. This introduces a next-generation Web Part infrastructure for the Microsoft Windows Server 2003 platform as shown in the following figure.
Figure 1. ASP.NET 2.0 Web Part infrastructure
Choosing Between ASP.NET 2.0 Web Parts and Windows SharePoint Services 3.0 Web Parts
Office SharePoint Server 2007 and Windows SharePoint Services 3.0 are built on top of the ASP.NET 2.0 Framework. Windows SharePoint Services 3.0 uses the ASP.NET 2.0 Web Part infrastructure to take advantage of features such as master pages and custom Web Part development while providing a complete set of Windows SharePoint Services features, such as document services, events, workflow, search, site columns, content types and more.
You can build Web Parts for Windows SharePoint Services 3.0 in two ways:
You should create ASP.NET 2.0 Web Parts whenever you can. However, there are a few exceptions where using SharePoint-based Web Parts might offer advantages… The following table provides a decision matrix to help you choose the best option depending on your business needs.
Create a custom ASP.NET 2.0 Web Part | |
|
Table 1. Decision matrix for creating Web Parts
Creating a New Web Part Solution
The Web Part project template included in the extensions is customized especially for creating Web Parts for the Windows SharePoint Services environment.
To create a new Web Part solution
By default, the code file for the Web Part contains the following:
Customizing the Web Part Solution Package
The Web Part project template automatically generates the XML files needed to package your Web Part as a Windows SharePoint Services 3.0 Feature for deployment and activation. The required GUIDs contained in the XML files are also generated automatically.
The extensions generate a .webpart file as the element.xml file for the Feature containing the Web Part. Every Web Part should have a .webpart file, which is an XML file that describes the Web Part. The .webpart file also makes your Web Part appear in the Web Part gallery in Windows SharePoint Services.
You can customize the information in these XML files by editing solution, Feature, and element properties on the SharePoint Solution tab in your project’s Properties dialog box, as follows:
Customizing the Web Part solution feature package
This tab lists the nodes that contain the properties for the solution package that the extensions will generate.
For example, click the Element node, and then edit the values for the Title, Description, and ImportErrorMessage keys.
Deploying and Debugging the Web Part
You can deploy and start debugging your Web Part simply by pressing F5.
When you press F5, the extensions automatically build, deploy, and initiate debugging of your Web Part solution Feature. To accomplish this, the extensions perform the following actions automatically:
Deploying and debugging your Web Part
Additional resources and references
Please refer to following link for more information:
http://msdn.microsoft.com/rampup
Stsadm only returned text, but Powershell can return .net Framework Objects as well. Powershell can also give you access to external data stores unlike Stsadm. Stsadm is not completely dead but it is very close because Powershell does everything that Stsadm does or even much more. We can manage our SP 2010 farm without Powershell but it will be like managing CRUD functionally while connecting External data in BDC services.
The Exchange Management Shell is a powerful command-line management interface, built on Windows PowerShell v2, which enables you to administer every part of Microsoft Exchange Server 2010. You can be an administrator who needs to perform day-to-day management of your mailboxes, or you can be a developer who needs to automate administration using a custom line of business application. Either way, the Shell enables you to do more, faster.
The Shell lies at the heart of the administration model in Exchange 2010. Both the Exchange Management Console (EMC) and the Exchange 2010 web interface use the Shell to process actions. When you view a mailbox, create a distribution group, or mount a database, the EMC and the web interface run a Shell command that performs the actual request. You can do everything in the Shell that can be done in the EMC or the web interface, and more. Later on in this article I’ll talk more about how you can use this versatility to your advantage and learn more about the Shell.
This article talks about the following:
A Few Basic Concepts
First, let’s get some basic concepts about the Shell out of the way.
For more information about each of these concepts, see Exchange Management Shell Basics in the Exchange 2010 online Help.
Role Based Access Control
Role Based Access Control (RBAC) is the permissions model in Exchange 2010. RBAC uses management roles to define what a user can do. For example, someone who’s assigned the RecipientManagement role can manage mailboxes, contacts, distribution groups, and other types of recipient objects. The management roles that are assigned to users can be scoped to allow users to manage only specific recipients or servers in an Exchange 2010 organization. If that assignment is scoped to only recipients in Seattle, the administrator will only be able to administer Seattle users and nobody else.
Note: |
This article discusses a beta release of Exchange 2010 and as such, functionality, composition of built-in roles, and usability are subject to change. |
Exchange 2010 has several built-in management roles that you can use out of the box to distribute permissions to your administrators and users. Some roles, such as OrganizationManagement and RecipientManagement, enable your administrators to manage other users. Some roles, such as MyOptions and MyDistributionGroups, enable your end users to manage their own mailbox and distribution groups. Who you assign roles to, and the roles each user is assigned, defines what each user can do in your organization.
RBAC and the Shell
So why is RBAC important in the Shell? As I discuss later in this article, when the Shell is started, it connects to an Exchange 2010 server and authenticates you. As part of the authentication process, Exchange 2010 checks RBAC to see what roles you’re assigned. Each management role has a list of cmdlets and their parameters that users assigned the role can use. When the Shell creates your environment, only the cmdlets and parameters that you can access are added to the environment.
The following diagram shows how both the EMC and the Shell connect to an Exchange 2010 server. The request for authentication is received by RBAC, which determines which roles you have, and therefore which cmdlets and parameters you have access to. On subsequent requests, Windows PowerShell and RBAC receive requests to run cmdlets, validate that the user is allowed to run the cmdlet, and then runs the cmdlets for the user.
Source <http://technet.microsoft.com/en-us/library/dd795097.aspx>
Stsadm command-line tool (Office SharePoint Server)
Updated: 2006-12-01
In this article:
Microsoft Office SharePoint Server 2007 includes the Stsadm tool for command-line administration of Office SharePoint Server 2007 servers and sites. Stsadm is located at the following path on the drive where SharePoint Products and Technologies is installed: %COMMONPROGRAMFILES%\microsoft shared\web server extensions\12\bin. You must be an administrator on the local computer to use Stsadm.
Stsadm provides a method for performing the Office SharePoint Server 2007 administration tasks at the command line or by using batch files or scripts. Stsadm provides access to operations not available by using the Central Administration site, such as changing the administration port. The command-line tool has a more streamlined interface than Central Administration, and it allows you to perform the same tasks. There are certain operations and certain parameters that are only available by using the Stsadm command-line tool.
Using Stsadm
The command-line tool provides access to the complete set of Office SharePoint Server 2007 operations. You can use Stsadm from the command line or with batch files or scripts. Stsadm must be run on the server itself.
To use Stsadm, you must be a member of the local Administrators group on the server. When you invoke Stsadm, you supply an operation and a set of command-line parameters in the form:
-operation OperationName -parameter value
Note: |
If a value you need to use with the command-line tool includes a space or a character that is treated as special by the command-line interface, such as an ampersand (&), you can enclose the string in quotation marks (“). For example, if the URL to a site is http://my site, you can enter the URL as “http://my site“. |
Most parameters for the command line also have a short form that you can use instead of the full parameter name. For example, the following command sets the configuration database to use Server1_collab on Server1 and specifies the database user name and password to connect with:
stsadm -o setconfigdb -connect -ds Server1 -dn Server1_collab -du User1 -dp password
The following table explains the commands and parameters from this example.
Command or parameter | Definition |
-o setconfigdb | Creates a connection between Office SharePoint Server 2007 and a configuration database. |
-connect | Specifies that there is an existing configuration database to use. |
-ds Server1 | Specifies the server name that contains the database to use. |
-dn Server1_collab | Specifies the database name to use on that server. |
-du User1 | Specifies an administrator user name for the database. |
-dp password | Specifies the password for the user. |
Stsadm is not interactive
Stsadm is not an interactive tool. With Stsadm, you type the operation and parameters all at once. You will not be prompted to fill in missing parameters while the operation is running. If a required parameter is missing, the operation fails, and you must type the operation and parameters again.
This behavior allows better flexibility for batching commands, because the tools do not prompt you for information after you have submitted a command. If you want a more interactive tool, try using the administrative object model or Central Administration pages.
Available operations and properties
For a complete list of Stsadm operations and properties, see Index for Stsadm operations and properties (Office SharePoint Server).
The following operations are available only from the command line:
addcontentdb (the command line is required for adding databases that need to be upgraded) | enumsolutions | renameserver |
addsolution | enumtemplates | restore (site collection level) |
addwppack | enumwppacks | retractsolution |
backup (site collection level) | execadmsvcjobs | retractwppack |
binddrservice | export | scanforfeatures |
canceldeployment | forcedeletelist | setadminport |
copyappbincontent | getadminport | setconfigdb |
createadminvs | getproperty | setproperty |
createsiteinnewdb | getsitelock | setworkflowconfig |
databaserepair | import | spsearchdiacriticsensitive |
deleteadminvs | installfeature | syncsolution |
deleteconfigdb | migrateuser | uninstallfeature |
deletesolution | provisionservice | unregisterwsswriter |
deletewppack | refreshdms | updateaccountpassword |
deploysolution | refreshsitedms | updatealerttemplates |
deploywppack | registerwsswriter | updatefarmcredentials |
displaysolution | removedrservice | upgradesolution |
enumdeployments | removesolutiondeploymentlock |
The following parameters are available only from the command line:
-force | -propertyname |
-globalinstall | -propertyvalue |
-newname | -servicename |
-overwrite | -ssl |
Source <http://technet.microsoft.com/en-us/library/cc261956(office.12).aspx>