Macsql.cfg error ...except XP Pro

[mystifying]

We have just recently had a major server crash and had to rebuild. Part of the process required us to reinstall Macola and restore the database from backup. We've made it through that ok and have our users back, etc but are having a problem with PWE on a couple workstations (not all). The problem is we get the error "The macsql.cfg is either missing or does not contain the necessary information..." on some workstations. The workstations that do NOT get this error are XP Pro stations. The ones that DO get this error (when logging in through PWE only) are Win 98 or Win2000 Pro machines. I have already checked all the permissions I could think of. Any suggestions?

 

[vbajock]

Macola root mapped to M: ?

 

[mystifying]

Yes, well we actually use the L drive (M was taken at the time we set up), but mapping seems ok on all the problem systems. I've tried reinstalling Macola and SQL on some of these stations, but still no luck.

 

[Rob7]

mystifying,
You might take a look at the Macola7.ini on the machines you are having a problem with and compare them to the Macola.ini files on the ones that are working. There might be a Macola root path error or something else not quite right.

Rob

 

[dgillz]

Is the company setup set to look at drive L ? Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

dgilsdorf@trianglepartners.com

 

[MacolaHelp]

Sounds like some of the machines might not have all the isolve data sources for all the companies. Reinstalling the macola client will usually correct this, or manually recreating the DSNs. Did you double check the cfg file to be sure that the # of companies = the actual installed (including macola electronics) & that the companies are all listed in the cfg? I have seen it happen on 98 machines that creating a new company doesn't always put it in the cfg file. Might be because the user wasn't administrator on the network at the time they created the company, so only portions of the setup were completed.

 

[mystifying]

I was wrong in that it was only XP Pro machines working properly, the two XP Pro machines are working fine, along with one Win98. Nothing is in common (at least obviously) between the good machines and/ or users. Everything seems to be mapped and listed in the company setup properly and the macsql.cfg file looks right. I've checked the macola7.ini file and compared against a good machine ...it all looks ok there.

I spent a couple hours with tech support yesterday with no luck. The suggested I set up a stand-alone system with a single user version of SQL and Macola on it and copy over the PWE, macsql, and Prosql files and see if that fixes it, but I haven't gotten to that just yet. They sent me new copies of pwe and macsql already and that didn't fix it, so I have my doubts the suggestion they made will work, but I'll give it a shot. Other than that, I'm out of options and rather frustrated.

 

[Rob7]

You may have to reinstall Macola. If you do that, Make sure you back up the database then remove it through add/remove programs. Then, go to the Macola root and delete whatever is left. Then go to each workstation and using add/remove, take out the Macola client. This will give you a clean slate to start over again. I know this is a bad deal but I have had to do this before. SOmeimes it is better to start again.

Rob

 

[mystifying]

Just and update ...I tried replacing the files tech support suggested, but with no luck. I will probably end up just reinstalling it looks like. Thanks for the help/ suggestions.

Stacy

 

[MacolaHelp]

mystifying: A thought: did you change the server name when you rebuilt? I have had the unfortunate experience of trying to rename a production SQL server & move databases to a new server that involved many nights & the better part of two weekends to resolve. In trying to eliminate some of the dba issues, the client's in house sql expert elected to use scripts to create the users on the new sql box. To make a long story short, because of the way macola creates the users through the visual menu builder, it was not happy to have the users created externally & several of them were corrupted. We gave those users new IDs in the end. Even re-installing Macola didn't help this problem & sql has something buried deep inside the registry & security with user IDs that have already been created. Even deleting the corrupted users doesn't allow you to re-create properly. Another FYI is that detaching, moving & reattaching a macola db seems to work better than using DTS & it is much faster.

 

[vbajock]

You can also create big problems if you do a clean install of Win 2K server and then give the server the same name as the old box.