ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Installation >> Win7 64 vs 32 bit
http://www.istechforum.com/YaBB.pl?num=1280861655

Message started by David Waldmann on 08/03/10 at 11:54:14

Title: Win7 64 vs 32 bit
Post by David Waldmann on 08/03/10 at 11:54:14

I have been going round and round with Evo on my Win7-64 machine. Finally had it going good and solid for several months and then did the 7/5 update and it's broke again. Actually, it worked fine the first day of the update, including starting and quitting Evo several times and at least one system reboot in there. Then the next day, bang! You're dead.

I'm wondering how much of the problem might be Win7 vs 64-bit. Anyone have any words of wisdom or testimonials? BTW, DBA Classic works fine on here, if a bit slow.

Title: Re: Win7 64 vs 32 bit
Post by RPCAdmin on 08/03/10 at 12:40:04

Hmm... 7 stations here using Win7-64 bit.  No issues - Pervasive 2000i (is it sp3 or sp4?)....I know that one or two of the stations was a little finicky on the initial setup - Lynn's faq had something about running S:\dbamfg\evoerp.exe   S:\dbamfg - not sure if we did that or not.  No real help here.

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/03/10 at 13:32:30


RPCAdmin wrote:
Lynn's faq had something about running S:\dbamfg\evoerp.exe   S:\dbamfg - not sure if we did that or not.  No real help here.


Yes, I did that. I also had to use UNC drive mapping. I thought I (well, with Malcolm's help) had it fixed...  :'(

Title: Re: Win7 64 vs 32 bit
Post by RPCAdmin on 08/04/10 at 03:48:12

One thing I have noticed with Vista and to a certain extent much less with Win7 is that occasionally, it will not have the mapping fully active to the server (that is the best way I can describe it).  Sometimes a user will try to open Evo, get an error....and if you try to open the mapped drive in explorer (it takes a few extra seconds, but finally opens) and then EVO will run fine.  Strange behavior, but it doesn't happen too often.

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/04/10 at 03:58:19

I have noticed in Win7 that sometimes in File>Open or File>SaveAs dialogs that it will show that drives are not connected (red "x" on them). However, I just tried Evo with a Win Explorer window open to both the applications and data folders; no luck...

Title: Re: Win7 64 vs 32 bit
Post by RPCAdmin on 08/04/10 at 04:16:31

Have you tried running EvoERPsetup.exe?  Just to make sure all the directory pointers are correct.  Also, what error do you get when you try to run EVO?

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/04/10 at 04:36:24

EvoERPSetup.exe shows the correct UNC drive mapping.

Here is a sequence of what happens:

(first of all, I have to run Evo as administrator, so I have to say "yes, I really want to do this)

I get the logon window, then:

FILE OPEN ERROR
Error number 12
File was not found
File name: BKSYMSTR
Program name: \\SBSR2\APPS\DBAMFG\EOVOERMENU.RWN
EXE path: C:\ISTS\
This program will now end.

After I close that, I get a message about opening a file that doesn't exist, or something like that on BKSY.COMP.NAME, and then what looks like the Evo window but with no buttons on it.

UPDATE:

Just for the fun of it, I decided to uncheck "Run as Administrator", and now it works  [smiley=rolleyes.gif]

Edit:
Ooops. Spoke too soon. Evo opens, but many programs won't open - it just goes into "not responding" mode. Maintain Database works, TAS-G works. It seems that T7 programs work, but so far not a single BK or T6 one. And although T7SOA opened it hung when I did a lookup.

Something obviously is still wrong...

Title: Re: Win7 64 vs 32 bit
Post by RPCAdmin on 08/04/10 at 05:48:52

Yeah, well hopefully this will provide enough info to Lynn to help diagnose the problem.

Title: Re: Win7 64 vs 32 bit
Post by Lynn_Pantic on 08/04/10 at 07:03:13

T6 and BK programs load a second instance of the EXE.  Add TP7RUNTIME.EXE to your DEP exceptions and see if that helps.

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/04/10 at 07:41:00

Doesn't like DEP. Won't even try to start - I just get the Windows "this program has closed" as soon as I start it. I had TP7Runtime.exe and EvoERP.exe in both the local ISTS and server locations.


Title: Re: Win7 64 vs 32 bit
Post by Lynn_Pantic on 08/04/10 at 08:09:36

The difference between the T7 programs (that work) and the T6 & BK (that don't) is that the T6 & BK chain to a new instance of the TP7RUNTIME.EXE so somehow your workstation isn't liking that but I don't know why if it is not the DEP.

Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/04/10 at 09:48:04

I think you may be troubleshooting 2 problems...for now i think we should focus on the Disconnected Drive issue...(the red "x" on mapped drive letters).  From what I can tell, we need to know if it's a connection issue or some sort of local problem that makes it look like a server permission issue.

• Wired or Wireless?

• What AntiVirus program are you running?

• Right after boot up, open a DOS box.  Type "ping -t [evoServer]"  where [evoServer] is your Evo server's IP Address (please use the IP Address, not the name).  Let it run in the background for as long as you can, watching it as often as you can, but if you see a bunch of these "Request timed out", there might be a real network problem.

• Right after boot up, open Computer.  Do you see "the red x" on your mapped drive?  If so, launch Evo.  I expect you'll get an error - please take a screen capture.  Now back in Computer, double-click your Evo drive letter, then go back to the drive list, do you still see "the red x".  Open the Task Manager, kill Evo (and tp7runtime if it got that far) and then start Evo again.  Do you get an error?  Is the the same as the error you got last time?




In case anyone's wondering - I'm running Win7 Ultimate 64bit, Evo w/ 7/2010 update & psql10.10 (soon to be 10.30, since my testing has looked pretty good).

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/04/10 at 10:54:05

This is a wired network.

Running AVG 9.0 (paid version).

I ran the ping test, and after 15 or 20 minutes all the ones I've seen have been <1ms except when I first fired up Evo it dropped to 9 & 10ms. Not a single time out.

So far I have not been able to get a red X in Explorer.

However one thing you said makes me curious.

Quote:
Open the Task Manager, kill Evo (and tp7runtime if it got that far)


I don't get a tp7runtime showing in Task Manager even when Evo starts all the way up, not even on a good fully-working workstation... Should I be?

EDIT: just realized that Ctrl+Break shows the packet data. So far, sent 1139 packets, received 1139 packets. 0 lost.

Title: Re: Win7 64 vs 32 bit
Post by GasGiant on 08/04/10 at 11:23:52

tp7runtime.exe only runs when a BK or T6 program is called from the menu. However, since it is basically another instance of evoerp.exe, it needs to be killed before you attempt to restart Evo or Evo will quit without giving notice.

Title: Re: Win7 64 vs 32 bit
Post by Kelloggs on 08/04/10 at 11:31:31

We have a similar problem.

if we try to use the shortcut with "C:\ISTS\evoerp.exe C:\ISTS" target
we get the following error: Data dictionary file could not be opened:F:\DBAMFG\FILELOC.DBF

But

If you go to start  then run and then open F:\DBAMFG\evoerp.exe

It works ok

???

:-X

Kelloggs

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/04/10 at 11:54:03


GasGiant wrote:
tp7runtime.exe only runs when a BK or T6 program is called...


I see. And so it is (on a properly working machine). Never starts on the problem one.

Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/04/10 at 11:57:16

No, I'm sorry for the confusion.  I didn't mean it quite like that.  

When you run Evo (if it's set up right) it should start EVOERP.EXE.  While it Evo, running one of the menu programs can start TP7RUNTIME.EXE.  

I was trying to say that on the chance that you got far enough to start it, kill it.  What I didn't say was that we need to do it anyway, no matter how it was started, because it keeps us from chasing a whole array of phantom symptoms.

Well at this point, you have a decision to make.  if you want to take the wreckless approach (like I would), wipe and reinstall Windows.  If given the option, limit what it installs to just the Operating System.  Then install Pervasive's 32bit client, run the Evo workstation setup - USING THE UNC with the server's IP address instead of it's name - and run it.

In your email to me, you asked if you should go back to 32bit.  I say 'no'.  First, because I'm running 64bit Ultimate and LOVE IT!!!!!  Second, and probably more important, because I've seen this happen on 32bit Vista and Win7 too, so in this case I'd say there's no benefit.  

But if you want to take the safe route and troubleshoot the problem then it's time to start removing some variables.  First I'd run System Restore and go back to the oldest point possible.  Then I'd uninstall your AntiViirus, all the software and hardware you don't 'need' and using MSCONFIG, take all things 'not Microsoft' out of your startup. You'll also need to uninstall Evo, the same way you did last time, and all things Pervasive.  Then turn of the UAC and Reboot a few times. Reinstall the 32bit Pervasive client and Evo - USING THE UNC with the server's IP address instead of it's name.  If that doesn't work, then I'd have to see it.  

Of course, the downside to 'the safe approach' is that you run the risk of screwing up your system anyway with all the uninstalling and Shrug and Pray's (Plug and Play) attempts to reinstall stuff.  That's why I'd just reinstall in the first place.  Faster and much less thinking!  Plus I get the benefit of a clean slate!

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/04/10 at 12:02:39


Kelloggs wrote:
If you go to start  then run and then open F:\DBAMFG\evoerp.exe

It works ok


Very interesting. BK/T6 programs slow to open, and may SAY "not responding" for a second or three, but they do open and function.

Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/04/10 at 12:05:00


David Waldmann wrote:
[quote author=Kelloggs link=1280861655/0#14 date=1280950291]
If you go to start  then run and then open F:\DBAMFG\evoerp.exe

It works ok


Very interesting. BK/T6 programs slow to open, and may SAY "not responding" for a second or three, but they do open and function.[/quote]

Definitely proves that the problem is local BUT I wouldn't run it like that for any length of time.  EVOERP.EXE 'wants' to be run from the local ISTS folder.  

Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/04/10 at 12:16:05

I just had a flash thought.... Are you running Pervasive 2000i???  If not, then please disregard my ramblings...

If you are, Pervasive doesn't support it on Windows 7, much less 64bit.  NOT TO SAY that it doesn't work, because YES I have seen it work a few times.  But it does mean that it shouldn't be a surprise if it doesn't work because of changes to the way Windows works.

If you're feeling adventurous, try the psql10 client.  Again, i wouldn't run it like that for any length of time - you're just asking for data problems - but it's one more log for the fire.

Title: Re: Win7 64 vs 32 bit
Post by David Waldmann on 08/04/10 at 12:40:41


skyywalker wrote:
...run the Evo workstation setup - USING THE UNC with the server's IP address instead of it's name...


I'm unfamiliar with that format. Would it be 111.222.333.444\drive?


skyywalker wrote:
you asked if you should go back to 32bit... I've seen this happen on 32bit Vista and Win7 too


That's the answer I was expecting, but thanks.


skyywalker wrote:
I'd just reinstall. Faster and much less thinking!  Plus I get the benefit of a clean slate!


I think that's probably what I'll do.

Yes, I am running 2000i SP3. I had bought v10 a couple years ago when we got a new server and couldn't get it to run (can't remember why?) so I got rid of it. Maybe I should re-visit that, but DBA Classic runs flawlessly on Win7-64...

Title: Re: Win7 64 vs 32 bit
Post by GasGiant on 08/04/10 at 12:41:58

I'm running Win7 with 2000i without issues. Installed both PSQL and Evo (first run from server) in the "as administrator" mode and it has been trouble free for four months. Had many issues at first because IT installed PSQL client in normal mode. Evo was slow and buggy until I reinstalled.

Title: Re: Win7 64 vs 32 bit
Post by Kelloggs on 08/04/10 at 12:45:33

I forgot to mention that our server is Windows 2003 and only the Workstations are Windows 7 - 64



Kelloggs wrote:
We have a similar problem.

if we try to use the shortcut with "C:\ISTS\evoerp.exe C:\ISTS" target
we get the following error: Data dictionary file could not be opened:F:\DBAMFG\FILELOC.DBF

But

If you go to start  then run and then open F:\DBAMFG\evoerp.exe

It works ok

???

:-X

Kelloggs


Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/04/10 at 12:54:38

Yes, UNC would be "\\[server IP]\sharename".  The "\" or "backslash" is the button on your keyboard that shares the "|" character, not the one that shares "?".

Yes DBA Classic seems to be standing the test of time...and Windows versions...  I have a few guesses on why it doesn't tend to clash with Vista or 7, but I'll hold those for the conspiracy theory thread!  ;-)

Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/04/10 at 15:53:06


Kelloggs wrote:
We have a similar problem.

if we try to use the shortcut with "C:\ISTS\evoerp.exe C:\ISTS" target
we get the following error: Data dictionary file could not be opened:F:\DBAMFG\FILELOC.DBF

Kelloggs


Do you get an error number too?

Title: Re: Win7 64 vs 32 bit
Post by Kelloggs on 08/05/10 at 07:26:07

No, on the top of the windows says: "Fatal Error"

Kelloggs

Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/16/10 at 02:16:02


Kelloggs wrote:
No, on the top of the windows says: "Fatal Error"

Kelloggs


UGH - that's a tuff one.  if it's just the one workstation i'd probably start by uninstalling and reinstalling the pervasive and evo clients.  but if that doesn't work - or if you already did that - I'd say either work thru it with Lynn's support group or reinstall Windows...  ...And my vote's for the latter!

======
I've got a sneaking suspicion that if i took the time to collect data on this issue, I'd find that it's more common from a particular oem or two....but if i'm right, reinstalling <i>shouuuuld</i> take care of it since the hdd image probably isn't the same as the image from the restore dvd...  

just a thought!

Title: Re: Win7 64 vs 32 bit
Post by lesleys on 08/26/10 at 06:42:03

Please share the theory, installed windows & and now my DBA works like crap. Slow windows. Takes for ever to have screens pop up, no help files anymore. This is the worst upgrade I have done. I love doing an upgrade to make the system faster and in fact my system is slower. How do I fix this?

Title: Re: Win7 64 vs 32 bit
Post by skyywalker on 08/26/10 at 10:38:26


lesleys wrote:
Please share the theory, installed windows & and now my DBA works like crap. Slow windows. Takes for ever to have screens pop up, no help files anymore. This is the worst upgrade I have done. I love doing an upgrade to make the system faster and in fact my system is slower. How do I fix this?


Can you elaborate?  We need Windows/DBA/Pervasive version numbers...both before and after the 'install'.  

If you have more than one workstation, do you see the problem on other workstations?

Title: Re: Win7 64 vs 32 bit
Post by lesleys on 09/03/10 at 09:20:40

Did you get any help on this. I am in same situation. They loaded windows 7 on mine so we can work out any issues before proceeding with rest of company. It now taks longer to do same work?
We can not go forward if this is what is going to happen to all stations.

Title: Re: Win7 64 vs 32 bit
Post by GasGiant on 09/03/10 at 09:42:48

When installing the Pervasive client on the Win 7 machine, make sure to right click and install as admin

When in doubt, reinstall the client

The same when running Evo the first time from the server. Navigate to the EVERP or DBAMFG folder on the server and right click on evoerp.exe and run as admin.

You should also make sure that your anti virus software is not checking everything that runs from the EVOERP/DBAMFG folder.

My Win7 installation now runs Evo at the same speed in ran under XP

Title: Re: Win7 64 vs 32 bit
Post by MikeT on 11/12/10 at 06:30:36

Regarding the post about Windows 7 sometimes disconnecting network drives automatically, you can fix that so it doesnt give you an error. We recently installed win7 on some new engineering computers and I had to do this on one of them.

"In Windows 7 and Vista mapped network drives will disconnect themselves after a time and show a red cross on the drive icon. You will still be able to click on the drive and see/use the contents but applications that require a network drive will see them as disconnected and will not see files.If you try to disconnect the drive it will still sit there saying 'Disconnected Network Drive' - the only solution is to reboot.
This is because there is a default disconnect time for inactive network connections. To correct this and turn the autodisconnect off do the following:
Open the command prompt as Administrator - to do this either click Start\All Programs\Accessories and RIGHT click the Command Prompt icon then LEFT click Start as Administrator or type CMD into the search box and hold Control & Shift keys down then press enter.

In the Command box type:

net config server /autodisconnect:-1

and press return.

Reboot computer.
Your mapped network drives should now stay connected - this is a permanent fix.
Also - when connecting mapped drives to Vista or Windows 7 - connect them with the full domain name of the server i.e.   \\servername.domain.local\sharename  NOT \\servername\sharename - Vista/Windows 7 insist on full domain paths in order to reconnect. You can connect using just servername but if it needs to reconnect it will not find the server."

Title: Re: Win7 64 vs 32 bit
Post by RPCAdmin on 11/12/10 at 06:53:38

Interesting tidbit about the network drives - happens here frequently and is mildly annoying.....One question however - what if you don't have a domain and only have the network set up as a workgroup?

Title: Re: Win7 64 vs 32 bit
Post by MikeT on 11/12/10 at 07:29:05

I imagine if you just have a workgroup, then it will not require a domain in the path, since there isnt a domain that exists on the network. I've never had to test that since we use a domain, so try it out!

ISTech Support Forum » Powered by YaBB 2.1!
YaBB © 2000-2005. All Rights Reserved.