Macola 7.6.100a on W2K Terminal Services

[mlandi]

We recently added a TS box with the intent to roll out Macola connectivity to our outside Sales reps over a VPN. 7.6.100a is running on SQL server 2000 on it's own dedicated server. On the TS box I've installed the Progression Client, the SQL client network utility, and Flex using my domain account which is a member of Domain Admins. All works well until I try to connect through another user's TS session. All security/rights setting are appropriate. I constantly will get a "ConnectDLL Manager Error" after entering the Macola Username and Password. the details are as follows:

Type: ConnectDLLMan Connection Error.
Function: CConnectDLLMan::ConnectToDB
Server:
DB: SCREENS
UserID: SUPERVISOR_SQL

Provider Error:

COM Error: Error
Code = 0x80040154
Code meaning = Class not registered
Source =
Description =

I've tried everything that I could think of... Uninstalling and reinstalling with Add/Remove programs, and with the change user command. I also added the user to the Domain Admins group before reinstalling. Macola will still only run with "my" login. Has anyone experienced this issue? I appreciate your time. Thanks.

 

[MacolaHelp]

See macola infomine docs 01.511.401 & 01.535.847 which reference this error as a symptom of mdac & sql server odbc v3.7. They point to a workaround at microsoft's knowledge base. Usually, you must also give full control to all users to the macola folder in the registry on win2k in hkey local\software as well. Sometimes you also must give permissions to odbc & microsoft\vba if you have flex issues.

 

[chadt]

ummm....yeah.....Macola through Terminal Services or Citrix blows.

It runs good on NT4 but not 2000. The only solution that we have found to rid us of all errors including 198's is to put macola on the SQL box.

Crappy solution but it works.

 

[mlandi]

Thanks for the replies.... I checked the macola infomine docs and verified versions on my TS box - MDAC 2.6 & SQL server ODBC 3.8. The MS Q243349 points to a possible hotfix for odbcbcp.dll and sdlsrv32.dll (v3.7) but also states the the problem was corrected in MDAC 2.5. After verifying my file/component versions, I didn't change anything there. I also granted registry permissions (full control) to macola and odbc (hkey_local\software) but still get the same error. Even though my user is a member of the local administrators group, I also added his domain account with full control.

As far as Macola being on the SQL box, here's my general setup: Macola is running on W2K server on the same partition as SQL server 2K. There are two partitions on this box one for user/data storage and the other dedicated to macola and sql. The TS box is a glorified PC - W2K server SP3 and TS.

Thanks again for any help/thoughts.....

 

[MacolaHelp]

The 198 errors with Macola started happening when users applied sp3 to win2k terminal servers. Sp2 didn't have the same symptoms. Check doc 01.559.508 as well at infomine. They have listed some things that have helped. They also indicate that you can install the macola programs on the terminal server. I have 4 sites using TS or Citrix: 3 are pvsw & 1 is SQL & they are all working fine without installing the programs on terminal server. If your TS is a glorified PC, I would say that is the culprit. You shouldn't scrimp on the TS hardware. If you invest wisely in the TS server, you can save a ton of money on client workstation upgrades.

 

[chadt]

SP2 has the same problems. There are allot of other variables that could make 198's present though./

 

[jdavissrusa]

How did you install the Macola client, did you use "Add/Remove programs"? There are many problems to deal with on the installation before you get to the "198 errors". I have 25 people connecting through TS to macola. The most important thing is use the "add/remove programs" or the change user install at the command line. Setting up a default user is the easyest way to make sure everything works.

I can go over this in email if you like, I already have gotten my bumps and bruises from these types of installs.

 

[mlandi]

Through my macola reseller and ultimately through macola support, I got this response:

On Win2k terminal services with SQL 2000, the LCID error is usually the result of outdated or mismatched MDAC components.

Go to this link to download mdac 2.6 sp2 and apply that to the terminal server.

http://www.microsoft.com/downloads/...6c-4918-4250-b8bd-3794582c9089&DisplayLang=en

I downloaded and applied mdac 2.6 sp2. All is fine!!!

There's a lot of talk about the 198 errors and "knock on wood", I haven't had them. As far as installation, I tried both Add/Remove programs and the change user command. Installation was done while logged in as a domain admin. My glorified PC running TS is just a demo box. I will be investing in the hardware shortly to bring a "real" box on-line. Thanks all for your input.... color this one closed