PWE Login Error

[AKPolarBear]

We have never been able to fully use PWE (possible blessing in disguise)but have needs to use the RMA feature. Some of the users get a “can't connect to database error” followed with an “invalid name/password combination error” message. Other users have no problem. This has not been tried for all users, just a select few.
We are MSSQL based. All users can log on through Progression without any problems. We were having this type of problem or an error 52 issue prior to converting to SQL last year. I have checked the Macola site for info and really only found one clue relating to a DLL file which appears to be correct. I did notice another DLL file spelled the nearly the same way except for one letter missing in the name. The internal name, however, was the correct name of the file I was looking for. I thought this odd, but then remembered I was working with Macola! Any suggestions?

 

[grossow]

What authentication method is being use on SQL server? Make sure that it is set to mixed mode. Have you tried renaming the macola7.ini and the macola shared directory,then reinstalling Macola?

 

[AKPolarBear]

We use mixed mode. I have not done the second step and reinstalled Macola. I would have thought it would have fixed itself when we did the last upgrade.

 

[dgillz]

There is a document 00.816.372 entitled "Common problems with PWE" which has your error and a resolution explained as follows:

"Cannot Connect to Database"
Resolution:

1) Possible *.DLL file missing - check for C:\WINNT\SYSTEM32\EVBTR13.DLL (or C:\WINDOWS\SYSTEM\EVBTR13.DLL) - verify the Progression client was installed

2) Wrong version of SQLEncrypt.dll - Verify that the size of the .dll is 116kb, dated 05/19/1999 or later.

3) Give FULL CONTROL permissions to Macola and ODBC registry keys

I suspect the latter to be the issue.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[AKPolarBear]

I also found that document. Items 1 and 2 check out okay.
Item 3. I am not sure if checked the correct location for those. Where should they be and does being in a WTS environment make a difference?

 

[MacolaHelp]

I have had to delete the data_00 intersolv DSN on some machines at some SQL sites to deal w/PWE. Macola tries to load that limited edition btrieve dsn on the way in so that ICRs can run. In fact, you don't need any of the intersolv dsn links if using sql, but a reinstall or update of the macola client might put them back.

In addition, there are documented problems w/terminal server & SQL & I believe one of the tech docs suggests to NOT use PWE. Those of us that want to use tabs, RMA & ICR reports need to make some more noise so they will spend more time trying to get it to work better.

 

[AKPolarBear]

Funny, I don't see that information in the Macola sales brochure...

At one point, I was told that PWE was going to become the de facto interface. Thankfully not.

Yes, I would like to use RMA and ICR. Do you have any suggestions whom to contact at Macola that will actually listen?

 

[dgillz]

If you delete and re-add the DSN this *should* make sure the registry keys in question are set to full control. I would try that and let us know the results.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[MacolaHelp]

Macola can be used for either btrieve or sql, that's why they install the intersolv drivers for btrieve. You are creating your own dsn to your macola database that you can use for other apps besides macola, such as crystal, knowledge sync, ms office, etc. The PWE still interface will still be available in ES. About 1/2 my clients use PWE right now & it's great for a lot of things: organizing your tasks, linking to other spreadsheets, running compiled crystal reports & it also tracks the last time you ran a task (very helpful for month end processing).

You can also create problems for yourself in SQL if you added these users through another application or in EM. Macola wants to add the users through VMB & there is something way down inside MSSQL that will almost never let you link a Macola user back up to the SQL user, sometimes not even if you delete in SQL & readd in VMB. I have one site in particular that must have separate user IDs for their 2 primary SQL apps, because they both want to create the SQL user inside the app.

 

[MacolaHelp]

Macola does not officially support mixed mode authentication, either. I would set the macola users up with problems as new users in the macola vmb & then synchronize sql security. That is the only trick I have found that works with users first created in EM or another app that also need to log into macola.