By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,294 Members | 2,687 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,294 IT Pros & Developers. It's quick & easy.

VB code exit error when run via scheduler giving exit code of (c000008f).

P: n/a
i have schedule a .exe of VB6.0 on a remote computer and when that exe
run
out i got this message in scheduler. operating system is window server
2003
where i have scheduled it. This program actually download a file from
ftp
location and then fill the database with ODBC driver to MYSQL and at
last
close that file and delete that file.
I don't get any error when i run that program without scheduler. Please
help
us to solve that problem. below i am giving you the report that
operating
system tell us to post to microsoft we have already post that but don't
know
what we do. this is the report
thanks
Sunny
Connoisseur Infotech Pvt. Ltd. http://www.econnoisseur.com

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="MLSimagelist.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="MLSimagelist.exe" SIZE="200704"
CHECKSUM="0xFD9DF62E" BIN_FILE_VERSION="1.0.0.0"
BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00"
COMPANY_NAME="connioseur" PRODUCT_NAME="MLSimagelist"
FILE_VERSION="1.00"
ORIGINAL_FILENAME="MLSimagelist.exe" INTERNAL_NAME="MLSimagelist"
VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4"
VERFILETYPE="0x1"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x3D1FD" LINKER_VERSION="0x10000"
UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0"
LINK_DATE="07/19/2005 14:59:03" UPTO_LINK_DATE="07/19/2005 14:59:03"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="MLSimagelisterr.exe" SIZE="200704"
CHECKSUM="0x8D46C82E" BIN_FILE_VERSION="1.0.0.0"
BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00"
COMPANY_NAME="connioseur" PRODUCT_NAME="MLSimagelist"
FILE_VERSION="1.00"
ORIGINAL_FILENAME="MLSimagelisterr.exe" INTERNAL_NAME="MLSimagelisterr"

VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4"
VERFILETYPE="0x1"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x31821" LINKER_VERSION="0x10000"
UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0"
LINK_DATE="07/25/2005 11:42:55" UPTO_LINK_DATE="07/25/2005 11:42:55"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="old\MLSimagelistdaily.exe" SIZE="204800"
CHECKSUM="0x1D3E1F34" BIN_FILE_VERSION="1.0.0.0"
BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00"
COMPANY_NAME="connioseur" PRODUCT_NAME="MLSimagelist"
FILE_VERSION="1.00"
ORIGINAL_FILENAME="MLSimagelist.exe" INTERNAL_NAME="MLSimagelist"
VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4"
VERFILETYPE="0x1"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x3D488" LINKER_VERSION="0x10000"
UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0"
LINK_DATE="07/15/2005 03:54:54" UPTO_LINK_DATE="07/15/2005 03:54:54"
VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="old\MLSimagelisttemp.exe" SIZE="200704"
CHECKSUM="0xFD761E2E" BIN_FILE_VERSION="1.0.0.0"
BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.00"
COMPANY_NAME="connioseur" PRODUCT_NAME="MLSimagelist"
FILE_VERSION="1.00"
ORIGINAL_FILENAME="MLSimagelist.exe" INTERNAL_NAME="MLSimagelist"
VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4"
VERFILETYPE="0x1"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x37246" LINKER_VERSION="0x10000"
UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0"
LINK_DATE="07/16/2005 03:51:36" UPTO_LINK_DATE="07/16/2005 03:51:36"
VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="1038336"
CHECKSUM="0x7C7BBFD9"
BIN_FILE_VERSION="5.2.3790.1830" BIN_PRODUCT_VERSION="5.2.3790.1830"
PRODUCT_VERSION="5.2.3790.1830" FILE_DESCRIPTION="Windows NT BASE API
Client
DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft®
Windows®
Operating System" FILE_VERSION="5.2.3790.1830
(srv03_sp1_rtm.050324-1447)"
ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32"
LEGAL_COPYRIGHT="©
Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32"
PE_CHECKSUM="0x10C135" LINKER_VERSION="0x50002"
UPTO_BIN_FILE_VERSION="5.2.3790.1830"
UPTO_BIN_PRODUCT_VERSION="5.2.3790.1830" LINK_DATE="03/25/2005
02:30:42"
UPTO_LINK_DATE="03/25/2005 02:30:42" VER_LANGUAGE="English (United
States)
[0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="1038336"
CHECKSUM="0x7C7BBFD9"
BIN_FILE_VERSION="5.2.3790.1830" BIN_PRODUCT_VERSION="5.2.3790.1830"
PRODUCT_VERSION="5.2.3790.1830" FILE_DESCRIPTION="Windows NT BASE API
Client
DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft®
Windows®
Operating System" FILE_VERSION="5.2.3790.1830
(srv03_sp1_rtm.050324-1447)"
ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32"
LEGAL_COPYRIGHT="©
Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32"
PE_CHECKSUM="0x10C135" LINKER_VERSION="0x50002"
UPTO_BIN_FILE_VERSION="5.2.3790.1830"
UPTO_BIN_PRODUCT_VERSION="5.2.3790.1830" LINK_DATE="03/25/2005
02:30:42"
UPTO_LINK_DATE="03/25/2005 02:30:42" VER_LANGUAGE="English (United
States)
[0x409]" />
</EXE>
</DATABASE>

Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

<co******************@gmail.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
i have schedule a .exe of VB6.0 on a remote computer and when that exe
run
out i got this message in scheduler. operating system is window server
2003
where i have scheduled it. This program actually download a file from
ftp
location and then fill the database with ODBC driver to MYSQL and at
last
close that file and delete that file.
I don't get any error when i run that program without scheduler. Please
help
us to solve that problem. below i am giving you the report that
operating
system tell us to post to microsoft we have already post that but don't
know
what we do. this is the report
thanks
Sunny
Connoisseur Infotech Pvt. Ltd. http://www.econnoisseur.com

<snipped>

Unfortunately this is one of those errors from the bowels of Windows that
speaks more about an inability to read an expected register (floats) that
where the actual error is coming from.

You need to provide more Error Handling in your application. That said - the
most common reason for this problem is the different
environment/user/permissions that the app is launched under. ie, system
account can't 'see' some resource. Perhaps a DSN, logical drive, ????

Would need more information. Add some more error handling and see if you can
pinpoint the exact area of problem. Comb your code for calls that depend on
the user of your app having some special knowledge or insight that is not
generally available to others.

hth
-ralph
Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.