Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SysPass not open and XP SP2 1

Status
Not open for further replies.
ThunderForest

ThunderForest

IS-IT--Management
Mar 3, 2003
189
US
See my Thread639-788591 (Syspass not open) and new Thread779-954630

Environment:

Macola 7.5.103d
bTrieve 6.15
Pervasive SQL 7.0
Novell 4.0
Platform: XP Pro, NetWare client 4.83 sp2

FYI: Netware client 4.9 does not support IPX and Netware versions below 5.0

Sorry if this seems like a double post, but it is a desparate time when your ERP cannot be accessed. I've also contacted MicroSoft. I was wondering if any Macola users with the above environment (if there are any left in the world) have experienced this problem:

With XP SP1 and the above environment, no problem accessing Macola. Since XP SP2, none of my XP machines can access Macola. The firewall and new security features don't seem to be an issue, as one PC does not use the firewall.


Getting answers before I'm asked
is why I go to Tek-Tips.
 
Sort by date Sort by votes
bTrieve 6.15
Pervasive SQL 7.0
Click to expand...

These would seem to be mutually exclusive. Btrieve 6.15 is what Macola used BEFORE Pervasive SQL 7.0. Can you recheck your configuration?

Also, is this happening on all machines or just Windows XP Pro machines? I am not at all sure that the 16 bit client, which was all that existed with Btrieve 6.15, will work on XP.

More info please.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
askdon@srhconsulting.com
 
Upvote 0 Downvote
Can you confirm that the Pervasive client install on the machines in question is the 32 bit client?

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
askdon@srhconsulting.com
 
Upvote 0 Downvote
Yes, it is 32 bit. According to a response I received in thread779-954630, it looks like Pervasive SQL 8.0 SP2 may correct the XP SP2 problem. I'm still waiting to hear back from Pervasive on this, as I want to be sure they support my version of Macola in this environment. Would you happen to know? BTW, getting back to bTrieve 6.15, are you saying I don't even need to be loading this on the Netware server? I thought Macola required this (bTrieve.NLM?).

Getting answers before I'm asked
is why I go to Tek-Tips.
 
Upvote 0 Downvote
You have the question bacwards.

The issue is not weather Pervaive supports it, it is weather Exact supports it. Exact does not support Pervasive SQL v7, which you are currently using. Nor do they support v8.0, however they do support v8.5.

DO NOT purchase a Pervasive upgrade from anyone other than Exact or your Exact business partner. It will not work with Macola unless you also purchase the pervasive reg byte from Macola.

By the way what has your Exact Business Partner or Exact had to say on this issue? This is 100 times more important than anything Pervasive has to say, IMHO.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
askdon@srhconsulting.com
 
Upvote 0 Downvote
Thanks. Sincerely appreciate your comments. I wasn't aware of that relationship. I've contacted our VAR. I'm somewhat reluctant to deal with Exact on any support issues because they no longer support our environment, and our VAR's typical solution tends to be "upgrade". Unfortunately, I need to continue bandaid-ing this environment because upgrading Macola is not an inexpensive option for this particular business.

Getting answers before I'm asked
is why I go to Tek-Tips.
 
Upvote 0 Downvote
Netware 4x hasn't been supported by Macola for at least 2 years. I would assume that pervasive 8.5 would run on NW4x, but you need to ask clarification from pervasive or your BP on this. If you purchase from Macola, though, & have problems, they may not be much help as they will not have tested the install on a netware 4x server. Is there some reason you are buying XP workstations with the latest & greatest service packs, but leaving your network running your business system on a configuration that is 5 years old? It sounds like it may be costing you more to try to maintain connectivity than it might to update your server/macola infrastructure. Pervasive cannot support your Macola installation. Macola would not have tested 103d on pervasive 8.5, either. Unless you have a ton of custom programs that would need to be rewritten, what is the hesitation to upgrade? Maybe you should consider the move to SQL? How many servers do you have? If you already have an SQL server, the decision may be easier than you think.
 
Upvote 0 Downvote
I really appreciate your response. Moving to SQL is perhaps far down the road for this company. The hesitation to upgrade are pure and simple costs, and that is beyond my control. However, if there is no alternative, then I have to present it that way to get it done. On the other hand, I'm sure many are using XP Pro and Windows 98SE and Macola/Pervasive. Do you think it's Netware 4.x causing the problem? If I upgraded to at least Macola v7.6.3 on a Netware 4.1 server, would it work with Windows 98 "SE" and XP Pro clients, or should I also upgrade Netware to at least v5.0? It is my understanding v7.6.2/3 does not work with Windows 98, as Exact told me:

"Currently, a workstation must be at least Windows 98 SE to run 7.6.200, Windows 98 OEM will not work with 7.6.200."

I'm communicating with our VAR, but would appreciate any comments you have. Happy Holidays. Thanks.


Getting answers before I'm asked
is why I go to Tek-Tips.
 
Upvote 0 Downvote
The only 98 client workstations I have still left running are on NW5x servers, pervasive sql2000i sp4 at the least, and they are in the process of replacing their server to move to a windows sql server. I never had success trying to attach xp workstations to a 4x server running btrieve 6.15 & frankly told the client that they were spending much more to attempt to make it work than they would have to replace the server. Or they could at least have invested the support dollars toward the server cost. I am not suggesting you upgrade to 7.6.300 in your environment, but rather that you should purchase a new server and upgrade macola on the new server. Another reason to move off NW4x was its limited support of tcp/ip. NW 5x & above used tcp/ip as a native protocol. You could purchase pervasive 8.5 or sql for your new server.

NW4x isn't "causing a problem". In fact, it will probably keep running after your first windows server dies. The problem lies with the application development which is geared to the windows world, to windows communication and integration models. Each iteration of a new windows OS buries the DOS level deeper, forces more hoops to integrate with a legacy network OS. I still have clients running 3.12 servers, but only in very limited roles.

If you purchase a new server, you can leave the netware workhorse doing what it does best: file & print services, log in management (if it currently does so), email (if it currently does so), etc. Buy your new server to manage applications. I find that macola sql 7.6.300 runs better on a windows server than macola psql2000i 7.6.300. But, in honesty, I have yet to try it with pervasive 8.5. I will do that soon with a netware 6.5 site & will have a better feel for its performance.

For several years now, as clients have replaced or added servers, I have had them buy servers configured to run the sql version, even if they plan to still run pervasive for the next couple of years. This way, when they are ready to migrate to sql, the server is in place & the software is up to the current version, making the database conversion much easier. Then they only need purchase the database upgrade from macola for $350/user & the SQL server license & CALs.

No, 7.6.200 & above will not run with win98 in general. Once in a while you get lucky, but it truly is luck only that makes it run. There are no magical configurations issues that will fix a broken 98 install, unless fdisk & reinstall OS & apps will do it. At that point in time, it's more economical to simply replace the computer.
 
Upvote 0 Downvote
Thanks. I'm not at all in disagreement with what you mentioned, would love to go that route, but I'm a solution provider for a small/meduim business that is hardly ready for the additional expense, let alone change. I know...sooner or later it will catch up with me.

Aside from all that, I solved the problem. Do not use the Novell client. Rather, use the Microsoft Client for Netware. Macola cranked right up after removing Netware client 4.83 SP2 and installing Microsoft Client for Netware. On another post I reported that Macola wouldn't work with Novell client 4.9 and XP, but now I wonder if it will since XP SP2 came out. Oh well, I have a band-aid now and.....famous last words..... if it ain't broke, don't fix it.

Getting answers before I'm asked
is why I go to Tek-Tips.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

prog_0927
  • Locked
  • Question
Macola inventory Tag count Process How Many Days Open?? 2
Replies
2
Views
895
dgillz
dgillz
prog_0927
  • Question
Received Not Invoiced Question
Replies
4
Views
596
dgillz
dgillz
prog_0927
  • Question
Variance Report Pre-post Not Matching Posting
Replies
5
Views
472
prog_0927
prog_0927
prog_0927
  • Locked
  • Question
AR Aging Report Not Matching
Replies
3
Views
256
prog_0927
prog_0927
prog_0927
  • Locked
  • Question
cus_item_no and OECUSITM_SQL 1
Replies
2
Views
140
prog_0927
prog_0927

Part and Inventory Search

Sponsor

Back
Top