Using telerik sitefinity with Arvixe shared plans

Technorati-tags: ,,

There are a lot of ways to install telerik sitefinity CMS on hosted web sites.
Doing it on Arvixe site is pretty easy since you have a lot of freedom Smiley

With this guide I want to show you how to do this step by step.
We will install a “Sitefinity Web CMS 4.0” site on a personal APS account.
This is the “smallest” account – it will also work with the bigger ones.
The only exception are VPS or dedicated hosts using “sitefinity direct installation”.


  1. Microsoft SQL Server Express 2008 installed (on your local machine if possible)
    You can also use a full SQL Server – just change your connection string before you deploy – this is described later!
  2. Sitefinity 4.0 RC downloaded and installed
  3. Visual Studio 2010 (express) installed
    This is not a must – I’ll also (shortly) point out, how to do the things with nothing more than FTP uploads.

First of all login to your Arvixe web panel.
Choose Database – SQL Server 2008


Choose new Database – give the thing a nice name and create it.


Since my site is “ManniAT” and it will be Sitefinity I combined booth somehow.

Next create a database user (optional – you can also use an existing user).


Be sure that the newly created database has a checkmark at this dialog.

Now notice: Database name, Database-User name and password

Next open SQL Express manager and create a new database.
Please excuse that the following (SQL Manager) screen shots are in German.


First choose create Database. In the following dialog give the database a name.

Be sure it is the same Database name you used in the Arvixe web panel.

Next go to “security/Logins” (Sicherheit/Anmeldungen in my screenshots) right click and choose “new login”.

In the following dialog take care and


  • Choose “SQL Server login”
  • Use exactly the name you used in the Arvixe web panel for the database user
  • Use exactly the same password you used in the Arvixe web panel for the database user password
  • Remove the checkmark at “Enforce Password policy”

In the same dialog navigate to “User assignment” check your newly created DB and in the list below check “db owner”.


Now we have created a database similar to the one on our Arvixe web space.

Next start sitefinity manager and create a new project. (Use a local path you can easily find later).

If you are new to Sitefinity or use the free community edition just check “Community edition” when asked for a license.
Else use your (purchased) license key.

Creating the project will launch your browser and the first dialog ask for a database to use.

In the following dialog ensure that you


  • Use SQL Server NOT SQL Express!
  • Use localhost\sqlexpress as your server name
    If your instance has a different name / port use this – in that case we will later change it to localhost\sqlexpress
  • Use the username and password as you choose when you created your SQL Express login.
  • Use the name of the database we created a step before.

This and the next steps need “full trust” for the web server (currently running on your local machine as “sitefinity server”).
Although Arvixe offers “full trust” (simply request it from support) there is no need for it in this case.
Sitefinity will run with “medium trust” after the database is initialized.

After setting the database your are asked to provide the “master user” for the new sitefinity site.


Take good care of this credentials! In the next dialog use the credentials to login to your new site.


From the top menu choose pages – and select create a page:


Give the page a title and a name.


Don’t care too much – we just create a page since this step (almost) finalizes database initialization.

The last step here is to add some content.


Drag a content control on you page and click edit content.


Enter some text and save it.
Choose Publish on the page menu.

Optionally you can set the new page as homepage.


You can also Click “View” to check if everything works so far.

With this step we have initialized our database – from now on sitefinity will run on “medium trust” (default on our Arvixe sites).

Close the browser.

Visual Studio users will now…

Choose “Edit in visual studio” from the sitefinity project manager.


    In Visual Studio create your masterpages, styles, items…
    Also create styles, templates and so on

If you use a different SQL Server than localhost\sqlexpress 1433 you must now change the database settings.

To do this locate


DataConfig.config in your VS project explorer.

Pure FTP Users will…

Locate this file with Explorer and open it using a text editor.

Both – VS and FTP:
If needed change the connection string.
data source=localhost\sqlexpress (no special ports).
User ID=YourDBUser

By the way – there are also tricks to run sitefinity locally against your Arvixe hosted database,
but that’s beyond the scope of this post.


Check out web.config – search for debug – if there is a setting “true” change it to “false” – this speeds up the things a lot (running on the server).

Now it’s time to deploy.
As FTP user choose the Sitefinity site root (the directory with web.config in it) and transfer it to wwwroot in your Arvixe web site.

Visual Studio users will…

First ensure that the configuration is set to “release”.
Next choose Build / publish from the menu.


This time use your Arvixe user account (the one you use to manage your site).

Also ensure (only for the first time) that “Delete existing files…” is selected.

Since FTP is not the fastest thing – we can do other things meanwhile.

End of separation…

From now on FTP and VS users will have to do the same things.
And both can do this will their files are transferred to Arvixe.

Go back to SQL Management studio, select your database and by clicking right choose Backup (Sichern here):


Start the backup – when it finished open the backup folder in explorer.


Right click on your backup file and choose “Send to / ZIP compressed folder”.
Our local work (except the running upload) is done.

Now open (again) your Arvixe Web panel.
Navigate to the database you created before and from “Maintenance tools”


Choose restore and select Uploaded file


Locate the zip we made before (using the browse button) and click restore.

Next navigate to the website you are using to host your Sitefinity site.

Since Sitefinity runs with .NET 4.0 go to Extensions and choose this.


We normally do not need Perl, PHP and CGI bin – therefor is disabled this (optional).
The only important thing is to select 4.0 integrated for ASP.NET.

Click Update NOW!!

Now we have to face a problem occurring with web services and authentication.
These services (without customization) support only one authentication schema.
This means we have to disable Windows Authentication.


Uncheck “Enable Integrated Windows Authentication” (last but one line).

IMPORTANT: this DISABLES settings at the site via Web Panel. Therefor other settings must be done BEFORE this step!
You can re-enable it later (for maintenance) – while it is enabled Sitefinity will not work!!
There are also tips on the Sitefinity website how to workaround this “problem” changing web.config.


After the upload (hopefully) had finished we should be able to see our “demo page” on our Arvixe site.
To logon to sitefinity simply add /sitefinity to your site url.
Example: http://www.mycoolsite.com
This will bring up your CMS Manager.

I hope this post was helpful.

Manfred AKA ManniAT

Tags: , , | Posted under 3rd Party Software | RSS 2.0

2 Comments on Using telerik sitefinity with Arvixe shared plans

  1. Markus says:

    Dear Manfred

    I try to get SF 4 RC running with my hosting provider without look so I tried and your article was most helpfull

    I would appreciate some feedback on can I contact you somehow? Phone, Messenger, Skype?

    Write to marktold @ if it would be possible. German is ok for me.


  2. Brynn Borton says:

    Are there any memory issues with this. Looking at other hodting providers the memory limit on the host is a problem with Sitefinity 4. I can’t find the memory limit for Arvixe.

Leave a Reply

Your email address will not be published. Required fields are marked *