Converting data store to sql

[Luvsql]

Currently, we have 6 citrix servers in a farm with the data store located within an access database on server 1. We have created a database on our sql server. We created a file dsn, pointing to the sql-server and marked to use the DataStore db that was created as the default.

We tried running the recommended DSMAINT MIGRATE, but it kept failing, so I DTS'd the tables from the access database into the new sql database.

We are trying to run the DSMAINT CONFIG in order to tell each server where the new data is, but it keeps failing:

Failed to connect to the datastore.
Please verify the parameters and data sources.

Is there a specific way this DSN needs to be created? Is the sa password stored somewhere within citrix now? Anyone done this successfully?

 

[Frankenherder]

I have done this quite easily.

Download the Advanced Concepts guide for Metaframe and it will walk you through it step by step.

Matt

 

[Luvsql]

We have that document and have done each step correctly, but it just is not working. The one thing I noticed is that the document says the migration "is only supported on MDAC 2.5" This is a very old version of MDAC and our applications require a min of 2.7, which we are running.

The issue directly revolves around the DSN. It wants us to create a file DSN, which we have. How did you create your DSN?

 

[ascotta]

I am pretty sure that MDAC 2.7 is runnable.
I think you may find that your DTS is responsible for it failing. Citrix instructions say and I quote "Don't mess with the tables etc" I did once and it broke the data store not unsurpriningly.

Why did the DSMAINT Migrate fail ? Is your farm still running on Access or is it broke till you get it transferred?

I have done it once to SQL and am about to repeat again on ORACLE.

I followed the destructions to the letter and it all worked first shot. Instructions in advanced concepts.

Cheers
Scott

 

[Luvsql]

The DTS was only a test and I restored afterwards to an empty database.

It's still running on access. The migration keeps failing with the error invalid DSN errors.

Do they not have a non-DOS way of doing this?

 

[ascotta]

Not that I am aware of.

I have just had a look on the site that I did and the DSN is a System one.

Cheers
Scott

 

[Frankenherder]

Change your SQL authentication on your new Datastore DB to SQL authentication instead of windows authentication. Creat a local user account and use that as your service account.

Like I said before, I did this process in like 10 minutes and was very straight forward. Make sure to go from the guide step by step.

Watch your spelling and syntax on the dsmaint command. Cut and paste from the Advance concepts to note pad then into your cmd window.

Matt

 

[Luvsql]

Our sql server is setup as mixed mode and our dsn is setup to use SQL authentication. I understand that it's very straight forward and that is what it is so frustrating when it's not working.

 

[Luvsql]

We have tried both a system dsn and a file dsn. Our file dsn has the following:

[ODBC]
DRIVER=SQL Server
UID=sa
AnsiNPW=No
QuotedId=No
AutoTranslate=No
Address=SQL-SERVER,1433
Network=DBMSSOCN
DATABASE=DataStore
WSID=CTX-XP-01
APP=Microsoft Open Database Connectivity
SERVER=SQL-SERVER
Description=SQL


We still get the error "invalid dsn" when running the command. We are using Microsoft SQL Server 2000. We have tried everything.