Hey folks,
I am working on an mvBase 1.03.02 system, (on Win NT 4.0 Server).
I shutdown the database cleanly, and temporariliy disabled the MV SRVCE &
mvWorkstation in NT "Services" - as I did not want mvBase starting on every
reboot of all these patches being applied, and then I applied numerous
outstanding MS Security Functionality Patches, including MSIE 6.0 SP1, (was
at MSIE 5.5), and the associated rebooting that goes with it.

Now that the platform OS is up to snuff, I went back in and Enabled MVSRVCE
and mvWorkstation in SERVICES, and started them. They appeared to start
without a problem.

I went to get into the database via "mvTerm" and laso Accuterm, and it says
I am "connected on line 0 or Line 1, but from that point on, I am dead in
the water!

Appreciate any insight or help anyone can provide!
Authorization looks to be still valid.
I did not move or corrupt the mvBase.00X files.

General Automation entries in Registry look to intact.

Help!

Regards,
Scott Richardson


--
Regards,
Scott Richardson
Senior Systems Engineer / Consultant
Marlborough, MA 01752
Email: CheetahFTL (AT) comcast (DOT) net
Web: http://home.comcast.net/~CheetahFTL/CC

Have you tried just starting the mvBASE as an application making sure the
autoboot is unticked ( This will automatically launch an mvTERM for you )

Then you can see if any errors come up

I have loaded most of the same NT4 updates as you except for the MSIE 6 and
I have had know issues

Craig

"Scott Richardson" <CheetahFTL (AT) attbi (DOT) com> wrote

Thanks Craig - did you mean to say you have loaded everything BUT MSIE6 SP1
and have NOT had any issues - or did you have some KNOWN issues?


"Craig" <nothere (AT) orthere (DOT) com> wrote

We also encountered glitches with mvBASE on NT 4.0 after loading
Microsoft updates, and others have too -- see Matthew's post on Sep
17.

After a month of agitating, RainingData is finally going to have an
engineer look the problem tomorrow and I'll post the results, if any.
In the meantime, we're moving off NT and onto Win2K Server where
mvBASE seems to run just fine.

David Ousele
deva at oregoncoast dot com

"David Ousele" <deva (AT) oregoncoast (DOT) com> wrote

Any word from Raining Data on this yet?

RainingData tech support used a VPN to log into our mvBASE on NT
system yesterday and verify that we actually do have a problem with
AUTO-LOGOFF (it doesn't recognize a disconnect when in a BASIC
routine). I understand that they'll try to set up an NT system that
reproduces the problem.

Since we've found a workaround and plan to move off NT anyway, I'm not
sure if they'll follow through on a specific fix for us, but if you
have a maintenance agreement, this might be a great time to pipe up.
:-)

David Ousele
deva at oregoncoast dot com


"Scott Richardson" <CheetahFTL (AT) attbi (DOT) com> wrote

"David Ousele" <deva (AT) oregoncoast (DOT) com> wrote

Interesting.
I discovered that although we updated the MS NT 4.0 Server Patches, we did
not bring mvBase up to recent Patch levels, (we normally use Patch 7 or 8
level), as 9 has not been tested yet in-house with our application.

Weird problem. Telnet sessions get a message - "Connected to mvBase Server
Line 0" but then just hang dead in the water. Good thing this is a back end
application database. I will alert my resolutin when I find it.

We're also on patch set 7, and since ours is a production server, I'm
reluctant to court disaster by loading anything else on it.

Have you contacted RainingData about this directly?

David Ousele
deva at oregoncoast dot com


"Scott Richardson" <CheetahFTL (AT) attbi (DOT) com> wrote