-William-
Did you define the environment variable DSMG_DIR which should be pointing to
the directory where the message repository resides?
To correct this, follow these steps:
1. Add the following line to the AUTOEXEC.BAT file:
SET DSMG=C:\WIN32APP\IBM\ADSM\ODBC\ADSM
Note: The directory path is from the previous ADSM version.
2. Reboot the machine.
3. Open a MS-DOS prompt and issue the "SET" command. The DSMG variable
should be there.
4. Retry the ODBC connection.
Thanks,
Demetrius Malbrough
-----Original Message-----
From: William Boyer [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 12:30 PM
To: [EMAIL PROTECTED]
Subject: ODBC Won't run after upgrade to client 4.1.2.0 Win32
I am running Win2K and I had TSM 4.1 client installed and was able to do all
my Crystal Reports with the ODBC driver. I upgraded to TSM 4.1.2.0 client
and followed the directions in the INSTALL.TXT for the ODBC driver. I
removed all my ODBC definitions, uninstalled TSM ODBC, rebooted and ran the
install for 4.1.2.0 ODBC. THe installation went just fine, i didn't need to
reboot anytime during the installation, which I take it to mean that I had
all the pre's installed already (MDAC, Installer...). I was able to define
my ODBC DSN's, but when I try to establish a connection from Crystal, I get
an error
"ODBC Error: [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on
SQL_HANDLE_ENV failed"
I followed all the directions in the installation documentation, but I am
still unable to get my reports to run. The TSM 4.1.2.0 client runs just
fine. When I display the driver versions in the ODBC connections dialog, it
says 4.1.2.0.
Bill Boyer
"Hit any user to continue!" - ???
