Restore same site collection to the same SQL Server

The question will be not is it possible or not. No, the question is. Is it recommend or not.

The short answer is. No it is not recommend!

One of our customers wanted to have a restore of his database from last sunday. He did not wanted to have a „really“ restore. No, he wanted to have the same database parallel on his Sharepoint server under a different name. He had some reason why to do that. That is not interesting here.

First we will think… why not. A restore is simple. This is like the same as if you want to transfer your database from one server to another one. Everything is ghosted within your database. Should be not a problem. But it is not working. MOSS 2007 is very intelligent here. And this is our luck.

If you create a new site collection in your Central Administration MOSS 2007 will write an GUID to his configuration database. You can take a look within the configuration database in the „SiteMap“ table. You will find the column ID which is a primary key. The same GUID is stored in your new created site collection. Take a look in the database of your new site collection on the „Sites“ table. Here you will find the same GUID within the ID column.

I think at this point is everything clear. If you restore the same site collection to the same database server so the same GUID will be written to the „SiteMap“ table on the configuration database. Because of that your database server do not accept the new entry. That is good because if it would be allowed may some settings of your production environment will be away or destroyed.

Personally I would not change just the ID within the „Sites“ table in your new created site collection. You do not know whats going on behind. Is the GUID is used somewhere else.

If you need to restore a database and want the same site collection with a different timestamp up and running parallel use another environment.

To figure out this problem take a look in you event log.

This error is related to the Event ID: 5763, Category: Database. Source: Windows SharePoint Services. Description: Primary key violation on SQL Server instance <servername> in database <configuration database name>. Additional error information from SQL Server is included below. Violation of PRIMARY KEY constraint ‚PK_SiteMap‘. Cannot insert duplicate key in object ‚dbo.SiteMap‘. The statement has been terminated.

Timo

Veröffentlicht unter Infrastructur, SQL | Kommentare deaktiviert für Restore same site collection to the same SQL Server

Registration

Hello,

Today I started to open a registration possiblity. If you are interesting just do it. Your are welcome.

Register here

Timo

Veröffentlicht unter General | Kommentare deaktiviert für Registration

Installing and configuring ADAM

This is a step by step guide how to configure ADAM

You can follow my instruction (which is just a short snapshot of it) or download the Adam_Step_By_Step_Guide here which helped me to configure ADAM. I will not post any screenshot here. If you need just download the guide from Microsoft. Note that the next 12 steps closed with the MS documentation. All other steps describe how to use user accounts within your ADAM instance.

1) Download ADAM free from here here or install ADAM directly from disc two of your Windows 2003 installation disc.

2) Run the installation wizard. When the installation is finished open your Start Menu. You will find a new entry named „ADAM“.

3) Start to create a new instance for ADAM. Click „Create an ADAM instance“. Note: Understand that is possible to use more than one instance of ADAM on the same machine listening on different ports. It is also possible to use Active Directory on the same machine as an ADAM installation.

4) On your first step within the wizard you have to choose „A unique instance“. This is because you create your first ADAM instance.

5) Then choose a new instance name. I will use „ADAMInstance“ here.

6) Next set up the ports which you want to use for your ADAM installation. Note: if you plan to install Active Directory on the same machine do not use the standard LDAP port 389 or 636 for SSL. Take any other port between 1025 and 65535. Think about what I wrote at the 3rd step. For now I will change my ports to 50000 for standard LDAP and 55000 for SSL.

7) Now set up your „Application Directory Partition“. You can do this later if you want but it will be easier for you to do this right now. You have to use a valid distinguishedName. I will use „CN=partition,DC=hell,DC=eu“.

8) At the next step you can choose a place to store the associated files with ADAM. I leave the default location to store my files.

9) Next you have to choose the account in which context ADAM service will run on your machine. You can use any domain account or let the standard account „Network service“. In my installation I will use the „Network service“ account. Note: the standard system service account is not a member of an Active Directory domain. Your ADAM instance will not be able to replicate with other ADAM instances on different computers. This is a standard security feature.

10) Choose the account or group that will have administrative privileges within ADAM. For my test instance I will simple use my current logged on user which is the administrator.

11) On the next step select the LDIF files which you want to import. I will import 3 files („MS-AZMan.LDF“, „MS-InetOrgPerson.LDF“, „MS-User.LDF“). Hint: For MOSS it is enough to use only the „MS-User.LDF“.

12) That’s all with the configuration. Finish up your installation.

For easier access to the configuration console configure 2 Management consoles

1) Type at the run menu „mmc /a“. On the file menu „Add / Remove a snap-in“. Add the „ADAM Schema“ to your console. When you are finished configure your console. On right mouse click select „Change the ADAM server“. Type your server name, in my case WSS, and your port number. My selected port number was 50000. Save and close the console.

2) Type at the run menu „mmc /a“. Ont the file menu „Add / Remove a snap-in“. Add the „ADAM ADSI Edit“ to your console. When you are finished configure your console. On right mouse click select „Connect to“. Type any name you want. I used „hell.eu“. For the servername you can choose localhost. Type you port number. My selected port number was 50000. Last but not least connect to a node. Select „Distinguished name (DN) or naming context“. Type you selected DN. In my case „CN=partition,DC=hell,DC=eu“. Save and close your console.

Now we should be able to create containers and users for future use. When you use ADAM you should be familar with the concept of Active Directory. As well you should know some properties. This will help you in your ADAM installation. Note that you do not have a nice GUI in ADAM. You are not working in a real Active Directory.

1) Open your „ADSI Edit“ console which you have defined above.

2) In the „Create Object“ wizard select „container“

3) Type „Users“. In this step we created just a user container to hold our user objects within the system.

4) On the next step click in your new created container and start the wizard again. Create new users. I called my users „testUser1“ and „testUser2“. When you have finished type a password for every user. Note: all new created users within your ADAM instance are disabled. To change that click on the user object and select the „msDS-UserAccountDisabled“ property. Set the value to false. If you don’t do that you will not be able to use that users as well you will not be able to see that users within your MOSS PeoplePicker dialog!

Now you will be able to use ADAM for whatever you want.

Some special notes for MOSS. If you want to use ADAM for you authentication you have to configure the „LDAPMembershipProvider“. ADAM needs read access to your instance. If you don’t configure you are not able to log on to your MOSS. Your PeoplePicker will not show any user.

1) Create a new user account within you server. I created „ADAMReader“

2) Now you have to set this account as read within ADAM. Just open your „ADSI Edit“ console for ADAM. Open the Roles container. Select the „Readers“ object. Right click, select „Properties“ and search for the „member“ property. Add your windows account. In my case „ADAMReader“.

Have fun with you ADAM installation. It is not that difficult to use and work with it.

Veröffentlicht unter Infrastructur | Kommentare deaktiviert für Installing and configuring ADAM

Sharepoint Conference 2008 in US

Microsoft’s biggest Sharepoint Conference in US will go on in March 3-6 at the Washington State Trade and Convention Center in Seattle, WA. I think it will be the biggest Sharepoint Conference which Microsoft ever made. They have great speakers and a lot of sessions there.

If you have any suggestions for session just write to Microsoft suggestions

Don’t miss and registrate soon as you can.

More informations Registration

Timo

Veröffentlicht unter Events | Kommentare deaktiviert für Sharepoint Conference 2008 in US

Sharepoint Conference 2008 in Europe

Ready.for.take.off

This is the motto of the Sharepoint Conference 2008 in Europe. But not only the Sharepoint Conference is going on. Much more important will be the launch of Visual Studio 2008, SQL Server 2008 and Windows Server 2008 which is going on due the same conference. It was suprising to me when I saw the date. The conference is going on between 19th to 21rd of february. The official launch in US of these products will go on 27th of february in Los Angeles at Microsoft’s Worldwide Partner Conference. So this will be a great day in europe.

Don’t miss and registrate soon as you can.

More informations Registration

Timo

Veröffentlicht unter Events | Kommentare deaktiviert für Sharepoint Conference 2008 in Europe