Error 26009. Could not Access the datastore using the DSN file, in the Scripting / Automation forum on BrianMadden.com
Brian Madden Logo
Your independent source for desktop virtualization, consumerization, and enterprise mobility management.

Error 26009. Could not Access the datastore using the DSN file, in the Scripting / Automation forum on BrianMadden.com

rated by 0 users
This post has 9 Replies | 1 Follower

Top 200 Contributor
Points 1,705
Erkan Zeki Posted: Tue, Apr 17 2007 6:29 AM
msiexec /a "\\uk911share\Images\Citrix Presentation Server\Citrix unattended\Java unattended\Java 2 Runtime Environment, SE v1.4.2_06.msi" /qb-! REBOOT="ReallySuppress" /liewa "%LOGFILE%.LOG"


msiexec /i "\\uk911share\Images\Citrix Presentation Server\PS4.0 for W2k3\MetaFrame Presentation Server\mps.msi" /qb-! CTX_MF_FARM_SELECTION="Join" CTX_MF_CREATE_FARM_DB_CHOICE="Thirdparty" CTX_MF_ZONE_NAME="Standard Zone" CTX_MF_SILENT_DSNFILE="\\uk911share\Images\Citrix Presentation Server\Citrix unattended\ODBC unattended\SQL.DSN" CTX_MF_ODBC_USER_NAME="Citrixima" CTX_MF_ODBC_PASSWORD="Thomas65" REBOOT="ReallySuppress" /liewa "%LOGFILE%.log" INSTALLDIR="%CTX_INSTPATH%"

-----------------------------------------------------

Here is my DSN file:-

ECHO [ODBC]"%TEMP%\SQL.DSN"
ECHO DRIVER=SQL Server"%TEMP%\SQL.DSN"
ECHO UID=%CTX_MF_ODBC_USER_NAME%"%TEMP%\SQL.DSN"
ECHO WSID=%COMPUTERNAME%"%TEMP%\SQL.DSN"
ECHO DATABASE=%CTX_DATASTORENAME%"%TEMP%\SQL.DSN"
ECHO APP=Citrix IMA"%TEMP%\SQL.DSN"
ECHO SERVER=%SQL_SRV%"%TEMP%\SQL.DSN"


Anyone have any ideas why my batch file is failing with the following error?

rror 26009. Could not Access the datastore using the DSN file, Username and password given function UseFileDSN returned failure in CTX_MF_IMA_Silent_ODBC
Action ended 11:03:38: InstallFinalize. Return value 3.

  • | Post Points: 50
Top 500 Contributor
Points 694
Porky replied on Tue, Apr 17 2007 7:40 AM
This is perhaps a silly question, but does the DSN file exist before you start the batch call? If it does not when exactly is the DSN file created during the process? or is it supposed to access it across the network from the share? and who has access permissions to the share? and no doubt you've checked with the ODBC Manager the connection to the database? If all the answers are 'green' then it's back to the drawing board.
  • | Post Points: 20
Top 200 Contributor
Points 1,705
File is accessible over the network if that is your question? I interested if you can see any issue with the way I am using variables in the DSN file and if I have missed anything in the Batch file.

Thanks





  • | Post Points: 20
Guest replied on Thu, May 10 2007 10:24 AM
I am having the same problem. Did you find a resolution
  • | Post Points: 5
Top 200 Contributor
Points 1,090
Try running everything from a local drive. I have come across issues when installing Presentation Server from a network location. Always works when run from a local source.
  • | Post Points: 20
Top 150 Contributor
Points 1,230
If you're using windows authentication in sql, you have to specify domain name in the username field: domain\username
  • | Post Points: 20
Top 50 Contributor
Points 5,587
Having the same problem, creating the DSN file local and using a SQL ID to connect. I cannot think of what else I could be doing wrong. The SQL I am using has DBO on the DB and can install or do a chfarm with it manually....
Ryan
  • | Post Points: 20
Top 10 Contributor
Points 48,736
I think you will find that a lot of the environment variables you are trying to use don't exist, unless you are creating them somewhere else. I do something similar, echoing the computername to create the WSID= entry, with a batch file and that has always worked. Where are things like CTX_MF_ODBC_USER_NAME coming from?

Why is it called "Common Sense"? It doesn't seem all that common!

  • | Post Points: 5
Not Ranked
Points 325

Try specifying another port the SQL server connection. A "known error" is that SQL sometimes uses port 12001 and not 1433 as one would normally use.

Here is a dsn file you can try:

[ODBC]
DRIVER=SQL Server
UID=sql-user-name
Trusted_connection=No
Network=DBMSSOCN
DATABASE=CitrixDatastore
WSID=Terminal-Server-Name
APP=CitrixIMA
SERVER=SQL-Server-Name,12001
Description=XenApp 5 Datastore

Regards,

Tord Bergset
Thinmaster.com
ICA-Jackass

  • | Post Points: 20
Not Ranked
Points 5

I got the same problem, and the solution for me was to add the server in the hosts-file in the windows catalogue. The server i tried to connect to had two network-interfaces and that caused a problem for the servers connecting to one of the interfaces. Adding the static ip together with the servername (both full name and servername) worked for me.

Regards

Robert Björkman

  • | Post Points: 5
Page 1 of 1 (10 items) | RSS