Good ol syspass file not open

[ThunderForest]

Macola 7.5.103d
Pervasive bTrieve
Novell 4.11

Platform: XP Home, NetWare client 4.83 sp2

I've tried infomine 01.824.940, to no avail. Also, it isn't the \user\*.tmp problem. This PC could once access Macola. I suspect something else was installed on it since then, overwriting an older version of something that Macola needs. If using PWE, you get past the password prompt to the menus, but then you get the same error with any selection. I have an XP Pro box, same NetWare client, that can access Macola with no problem. Looks like you can't uninstall Macola, right? Also looks like when it gets installed it doesn't write over existing files. Any help would be appreciated.

Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[kscheeler]

To uninstall the Macola client I do the following:

Delete the folder c:\progam files\common files\macola shared
Delete the file c:\windows\macola7.ini
Delete the registry key hkey_local_machine\software\macola
Reboot

The Macola client should then reinstall completly along with Flexibiltiy and ERS if you have it under the version you are using.

The other thing that doc talks about is the permissions. Do you get the same error for a standard user and Admin as well?

Kevin Scheeler

 

[ThunderForest]

Did the uninstall. No go. Also get the same error on that PC no matter who is logged in on that PC. Incidentally, the error comes up before the Macola login prompt when using Macola32.exe.

Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[kscheeler]

Do you get any error's when running the Pervasive Function Executor?

Kevin Scheeler

 

[ThunderForest]

Can't use that PC now, as it's the co. pres. However, the function executor doesn't seem to do anything on my PC or the XP box that does work., i.e., I can't enter a file and open it, etc., and nothing lists in the drop down. Yesterday I did load Pervasive Setup (Win32) and was able to connect to the server.

Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[MacolaHelp]

Try the btrieve file maintenance utility if function executor doesn't do anything. It sounds like you are running btrieve v7. Do you log onto the PC as administrator & to novell as admin? You need to verify, but you are probably using spx if novell. Did someone take it off the workstation? Reconfigure pervasive. Maybe a microsoft update broke a pervasive or macola dll. Did you reinstall pervasive, too? What is the error you get?

 

[ThunderForest]

I can open tables using DDF-Ease.

I've tried logging in as Admin as well. SPX is there. When loading WBManage, bTrieve File Manager, interestingly enough I get this error:

MicroKernel error 94. The application encountered a permission error, then the table that I was trying to open lists on the error screen.

I uninstalled Pervasive, then reinstalled and got this error during the "Testing 32 bit bTrieve":

The bTrieve read/write test failed with error "The application encountered a permission error". Installscout will try a read only test to Sample.Btr instead.

In regEdt32, under HLMS, after right clicking on ODBC, Pervasive, Macola, bTrieve, objects all have Full Control. At a loss.


Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[vbajock]

I noticed on your first post that you are trying to run this on XP home. Why don't you upgrade to Pro and see if that solves your problem?

 

[ThunderForest]

Thanks. Just ordered it. I think it will solve quite a few performance issues as well. It lasted a year on the LAN, but now I know that XP Home means XP Home.

Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[MacolaHelp]

per pervasive's website: error 94 on netware can be due to read only status on pvsw folder on the network. Be sure to change in netware filer mode.

If you search for error 94 on their website, you'll find several docs that may be your solutions. I never had any luck running xp clients w/btrieve 6.15 on netware. It sounded like you had version 7, though, since you referenced the setup win32 program. XP might run ok with it, I just never tried.

 

[MacolaHelp]

03.192.809 macola infomine refers to some patches specific to xp & netware client 4.83. It is talking about newer netware OS, but the principles may apply to your situation, too.

 

[ThunderForest]

FYI...

After a brief nightmare period, I did the upgrade from XP Home to XP Pro. Had to do a clean install to another folder, due to some sort of hardware conflict. Installed Netware XP client 4.9, which turned out to be a no-no for Macola 7.5.103d on a Netware 4.11 server. That client does not support Netware below 5.0, so I reinstalled XP client 4.83 SP2 and was able to connect to the server. Reinstalled all related software. Checked permissions. Logged in as administrator. Still get Syspass not open before Macola login prompt. I noticed in the PVSW log, I get an 8505 and 8517 error, but the knowledgebase on Pervasive isn't much help. ????

Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[MacolaHelp]

Do you have a path to c:\pvsw & program files\common files\macola shared? Check from a command prompt. Netware scripts can be overwriting these paths. Can you run a btrieve maintenance load information on a macola btr file from this workstation? If so, you have the btrieve connection. Have you verified pervasive settings on the workstation, connection protocols & sending request to server not workstation? The 8505 & 8517 errors are referencing the workstation engine. You should be running a server engine & installing the client from the network pvsw folder. I am also remembering that btrieve 7 required some manual registry entries at times to force the client to use remote rather than local.

 

[ThunderForest]

I'll get back to you on this next week. The PC is the co. president's, and will be available all that week. Besides, I need to lie low after the upgrade ordeal.

Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[vbajock]

Old Vietnam saying: Lie low, try not to look too important, the enemy may be low on ammo!

 

[ThunderForest]

Thanks vbaJock. Let's hope so.

Ok, back again. The paths are there (c:\psvw, \common files\macola shared..) Maybe this will shed some light....

This is what I get when using ddfEase and opening a table:

the data definition includes an inconsistency
scaleable sql engine error 353

This is what I get when using Pervasive's installScout32:

03-29-2004 14:50:15 SQL Interface D 0000091C N\ISCOUT32.exe" SERVER1MFG E SSQL-47: An error occurred while locating the Scalable SQL Engine. Error code: 8013. Binding rule: lib:///*.exe;platform=w3;type=sce;version=1.00..1.ff

Then, I ran this test from the XP box:

---- Results of Communications Testing ----
--Information : -----
--Information : Test started on Mon Mar 29 12:51:07 2004
--Information : Engine to test : Btrieve
--Information : Transport : All Available
--Information : Test level : Communications Stress Test
--Information : Target name : M:\Macola70\DATA_02
--Information : -----
Step 1 : Establish the workstation environment.
--Information : Winsock description : WinSock 2.0
--Information : Winsock TCP/IP is available
--Information : Winsock SPX is available
--Information : Microsoft Networking API is available
--Information : NetWare API is available
--Information : NetWare NDS API is available
--Information : Access to Scalable SQL for Windows NT database names is available
Step 2 : Determine full target name.
--Information : Input target name is M:\MACOLA70\DATA_02
--Information : No IDSHOSTS file found.
--Information : Target does not appear to be IDS.
--Warning : NWDSReadObjectInfo : object M : status : fffffda7 (-601)
--Information : Calling NetWare API to parse input target.
--Information : Target server name SERVER1
--Information : Fully qualified name SERVER1\SYS:\MACOLA70\DATA_02
Step 3 : Resolve full target name into a network address.
--Information : Using NetWare API to query Novell Directory Services
--Warning : NWDSReadObjectInfo : object SERVER1 : status : fffffda7 (-601)
--Warning : Unable to resolve server name via Novell Directory Services
--Information : Using NetWare API to read NetWare Bindery
--Information : Target engine SPX address : 3680B8A1:000000000001:8059
--Information : Checking DNS for TCP/IP address of SERVER1.
--Warning : gethostbyname failed : 11004
--Warning : Unable to obtain TCP/IP address via DNS.
Step 4 : Establish a connection to the target engine.
--Information : Local SPX address : 00000200:00V0A1F295Z9
--Information : Winsock SPX connection established (0x00d0)
Step 5 : Send data to/receive data from target server.
--Information : Making Btrieve Version call with Winsock SPX.
--Information : Btrieve Version is 7.16 NetWare.
--Information : Beginning Winsock SPX Stress Test
--Information : Winsock SPX Stress test canceled by user
--Information : Total Winsock SPX requests processed : 439
Step 6 : Terminate the established connection.
--Information : Winsock SPX connection terminated successfully.
--Information : -----
--Information : Test completed on Mon Mar 29 12:51:30 2004
--Information : -----


Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[vbajock]

Looks like a protocol problem of some sort. Can you ping your server? You might also consider adding SPX/IPX to your protocols list in Network Properties

 

[MacolaHelp]

Use spx rather than tcpip in a netware 4.11 environment. Did you check to see if the scalable sql loaded on the server console? Your communications test says it cannot resolve the server name in NDS. Do you know why? You want to install the pvsw client using a unc path rather than a mapped drive to the pvsw folder on the network. Netware 4.11/pervasive 7 were picky about that. You may also need the most current novell service packs for 4.11 to have any hope of having xp clients communicate w/it. Novell's website has always been pretty good for knowledge base docs as well.

 

[ThunderForest]

What bothered me about all this is that it works on one XP box, but not this particular one. To make what is already a very long story as short as possible, it works now. Although you see in one of my threads above that I did reinstall the 4.83 SP2 Netware client, after doing it again just a few minutes ago, Macola can now be accessed. Good thing. I was just about out of bandaids. Next time, I'll kickstart rather than jumpstart. Thanks for all your help.

Getting answers before I'm asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[pronet74]

I had the same problem and this is how I fixed it. Look at your shortcut and see how it's pointing to the .exe

I had my share pointed to the n: drive, but the shortcut was pointing to

\\keystone1\macapps\macola70\macola32.exe

I changed it to

n:\macola70\macola32.exe and everything worked.

I don't know why it setup the icon that way, but hopefully this will help you.