Welcome to the VanDyke Software Forums

Join the discussion today!

Go Back   VanDyke Software Forums > Secure Shell


Thread Tools Display Modes
Old 02-25-2008, 11:35 AM
Xtos Xtos is offline
Registered User
Join Date: Jan 2008
Posts: 7
Vshell service stopping?

I looked thru the forum for something on this and couldn't find it. Is there any known issues of Vshell's service turning off on its own?
My current setup is vshell 2.3.7 on a windows 2000 server sp4. I have a remote desktop that connects to vshell with bitvise tunnelier. This is how I get my backups to my server. I'm transferring about 2gb of data transferring every night this way. But as of late it seems that the vshell service is turning off about every other day.
Am I the only one coming across this problem? Any help would be great.

Reply With Quote
Old 02-25-2008, 03:18 PM
kbarnette kbarnette is offline
VanDyke Technical Support
Join Date: Aug 2007
Posts: 587
Hi Xtos,

Is there anything in the System Event logs that would indicate the cause of the service shut down?

Also, Are there any errors at the end of the VShell log after the service stops?

Does the service stop during the transfer, after it is over or when it begins?
Reply With Quote
Old 02-25-2008, 03:33 PM
Xtos Xtos is offline
Registered User
Join Date: Jan 2008
Posts: 7
This was in the system event logs...

"The VanDyke Software: VShell service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 0 milliseconds: No action. "

There are no errors in the log file. It just stops in the middle of the transfer.

Reply With Quote
Old 02-25-2008, 04:42 PM
jjh jjh is offline
VanDyke Customer Support
Join Date: Feb 2004
Posts: 819
Hi Xtos.

Does it look like VShell is crashing?

Typically when users experience a crash in one of our
products, it is helpful to the development team if we
can receive the ".dmp" and crash.log files created
by Windows when the crash occurs.

To make sure that the most useful information is placed
in the ".dmp" file, please do the following:

1. Start / Run / drwtsn32.exe -i

This will ensure that the Dr. Watson application
is enabled as the default debugger, allowing a
crash dump and log file to be created when an
application fails.

2. Start / Run / drwtsn32.exe

3. When the Dr. Watson dialog comes up, please see that
you have the following options enabled:
- Number of Instructions: 10
- Number of Errors to save: 10
- Dump All Thread Contexts
- Append To Existing Log File
- Create Crash Dump File.

4. If you are running Windows XP/2003 or newer, please
ensure that the Crash Dump Type is set to "Full".

5. Look at the path for the "Log File Path" and the
"Crash Dump" settings in the entryboxes at the top of
the Dr. Watson dialog. These should be full path and
filename specifications, respectively. Take note of
the "Log File Path" (and the Crash Dump Path if it
is a different path than the Log File Path) for
future reference.

6. Click OK to save the settings and close the Dr.
Watson window.

Once you have configured Dr. Watson to create a useful
crash log and dump file, please:

1. Repeat the behavior that causes the crash.

2. Once the crash has occurred, browse to the folder
specified in the "Log File Path" in the Dr. Watson

3. ".dmp" files can often become rather large. If
possible, compress the .dmp file.

4. Send the user.dmp and crash.log files as attachments
to an email message. If necessary due to the size of
the .dmp file (compressed or otherwise), we can
arrange for a place to upload these files to our FTP

You can send those files to us at support@vandyke.com.

When you send your e-mail message, please also include your
VShell serial number. You might be able to upgrade to a
newer version for free depending on your date of purchase.


Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -6. The time now is 08:51 PM.