Windows Desktop VB.Net Apps Getting an error 1004 0x800A03EC reading Excel due to 0xC004F057 in Application...
up vote
0
down vote
favorite
We have several Windows Desktop Apps written in VB.2010 and VB.2017 that have been running for a long time at many customers. Then last week Tues, Nov 13, 2018 we started getting customers emails and calls saying the apps are getting an error 1004/0x800A03EC. No app updates where made. Worked one day then stopped.
It doesn't fail here. Tried on 4 different systems. W7/Excel 2013, W10 w/Office 365/Excel 2016.
The failures have happened on W10, 7 and 2012 R2.
Apps are just reading the excel file.
Code
Code to initialize ws
ExcelAppObj = New Excel.Application
ExcelAppObj.Visible = pVisible
WB = ExcelAppObj.Workbooks.Open(pFFn, True)
WS = pWB.Worksheets(1)
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
Dim War as object = WS.Range(Ss).Value
In the Application Event log we found this warning
Installation of the Proof of Purchase from the ACPI table failed. Error code:
0xC004F057
Just 2 prior was
The Software Protection service is starting.
Parameters:caller=EXCEL.EXE
which to me indicates that some component in Windows does not think it is genuine. I know that on the system that got the error above both Windows 2012 R2 and Office are genuine.
I am sure this is a MS bug. Can someone point me in the right direction and hopefully a MS fix??????
Thanks and Happy ThanksGiving!
excel windows
asked Nov 19 at 19:52
QuickBooksDev
53119
add a comment |
up vote
0
down vote
favorite
We have several Windows Desktop Apps written in VB.2010 and VB.2017 that have been running for a long time at many customers. Then last week Tues, Nov 13, 2018 we started getting customers emails and calls saying the apps are getting an error 1004/0x800A03EC. No app updates where made. Worked one day then stopped.
It doesn't fail here. Tried on 4 different systems. W7/Excel 2013, W10 w/Office 365/Excel 2016.
The failures have happened on W10, 7 and 2012 R2.
Apps are just reading the excel file.
Code
Code to initialize ws
ExcelAppObj = New Excel.Application
ExcelAppObj.Visible = pVisible
WB = ExcelAppObj.Workbooks.Open(pFFn, True)
WS = pWB.Worksheets(1)
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
Dim War as object = WS.Range(Ss).Value
In the Application Event log we found this warning
Installation of the Proof of Purchase from the ACPI table failed. Error code:
0xC004F057
Just 2 prior was
The Software Protection service is starting.
Parameters:caller=EXCEL.EXE
which to me indicates that some component in Windows does not think it is genuine. I know that on the system that got the error above both Windows 2012 R2 and Office are genuine.
I am sure this is a MS bug. Can someone point me in the right direction and hopefully a MS fix??????
Thanks and Happy ThanksGiving!
excel windows
asked Nov 19 at 19:52
QuickBooksDev
53119
So look at the updates that were applied to office in November, ie the 13th of November. support.microsoft.com/en-us/help/4461503/…
– Sorceri
Nov 19 at 20:31
I don't have access to my clients' machine but one told me that what was installed around that time was KB4467703 and KB4467697. Those update were not installed on my systems which are up to date. Even the client that did a system to get it working wants to get their system current again. Another client uninstalled the last 2 updates (I don't know the numbers) but didn't want to reboot for fear of updates being re-installed again.
– QuickBooksDev
Nov 20 at 22:07
I looked at another client's application event log and that excel warning (Installation of the Proof ofPurchase from the ACPI table failed. Error code ...:)is NOT there. So my only lead is gone.
– QuickBooksDev
Nov 21 at 15:16
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We have several Windows Desktop Apps written in VB.2010 and VB.2017 that have been running for a long time at many customers. Then last week Tues, Nov 13, 2018 we started getting customers emails and calls saying the apps are getting an error 1004/0x800A03EC. No app updates where made. Worked one day then stopped.
It doesn't fail here. Tried on 4 different systems. W7/Excel 2013, W10 w/Office 365/Excel 2016.
The failures have happened on W10, 7 and 2012 R2.
Apps are just reading the excel file.
Code
Code to initialize ws
ExcelAppObj = New Excel.Application
ExcelAppObj.Visible = pVisible
WB = ExcelAppObj.Workbooks.Open(pFFn, True)
WS = pWB.Worksheets(1)
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
Dim War as object = WS.Range(Ss).Value
In the Application Event log we found this warning
Installation of the Proof of Purchase from the ACPI table failed. Error code:
0xC004F057
Just 2 prior was
The Software Protection service is starting.
Parameters:caller=EXCEL.EXE
which to me indicates that some component in Windows does not think it is genuine. I know that on the system that got the error above both Windows 2012 R2 and Office are genuine.
I am sure this is a MS bug. Can someone point me in the right direction and hopefully a MS fix??????
Thanks and Happy ThanksGiving!
excel windows
asked Nov 19 at 19:52
QuickBooksDev
53119
We have several Windows Desktop Apps written in VB.2010 and VB.2017 that have been running for a long time at many customers. Then last week Tues, Nov 13, 2018 we started getting customers emails and calls saying the apps are getting an error 1004/0x800A03EC. No app updates where made. Worked one day then stopped.
It doesn't fail here. Tried on 4 different systems. W7/Excel 2013, W10 w/Office 365/Excel 2016.
The failures have happened on W10, 7 and 2012 R2.
Apps are just reading the excel file.
Code
Code to initialize ws
ExcelAppObj = New Excel.Application
ExcelAppObj.Visible = pVisible
WB = ExcelAppObj.Workbooks.Open(pFFn, True)
WS = pWB.Worksheets(1)
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
Dim War as object = WS.Range(Ss).Value
In the Application Event log we found this warning
Installation of the Proof of Purchase from the ACPI table failed. Error code:
0xC004F057
Just 2 prior was
The Software Protection service is starting.
Parameters:caller=EXCEL.EXE
which to me indicates that some component in Windows does not think it is genuine. I know that on the system that got the error above both Windows 2012 R2 and Office are genuine.
I am sure this is a MS bug. Can someone point me in the right direction and hopefully a MS fix??????
Thanks and Happy ThanksGiving!
excel windows
excel windows
asked Nov 19 at 19:52
QuickBooksDev
53119
asked Nov 19 at 19:52
QuickBooksDev
53119
edited Nov 19 at 20:24
asked Nov 19 at 19:52
QuickBooksDev
53119
asked Nov 19 at 19:52
QuickBooksDev
53119
asked Nov 19 at 19:52
QuickBooksDev
53119
53119
So look at the updates that were applied to office in November, ie the 13th of November. support.microsoft.com/en-us/help/4461503/…
– Sorceri
Nov 19 at 20:31
I don't have access to my clients' machine but one told me that what was installed around that time was KB4467703 and KB4467697. Those update were not installed on my systems which are up to date. Even the client that did a system to get it working wants to get their system current again. Another client uninstalled the last 2 updates (I don't know the numbers) but didn't want to reboot for fear of updates being re-installed again.
– QuickBooksDev
Nov 20 at 22:07
I looked at another client's application event log and that excel warning (Installation of the Proof ofPurchase from the ACPI table failed. Error code ...:)is NOT there. So my only lead is gone.
– QuickBooksDev
Nov 21 at 15:16
add a comment |
So look at the updates that were applied to office in November, ie the 13th of November. support.microsoft.com/en-us/help/4461503/…
– Sorceri
Nov 19 at 20:31
I don't have access to my clients' machine but one told me that what was installed around that time was KB4467703 and KB4467697. Those update were not installed on my systems which are up to date. Even the client that did a system to get it working wants to get their system current again. Another client uninstalled the last 2 updates (I don't know the numbers) but didn't want to reboot for fear of updates being re-installed again.
– QuickBooksDev
Nov 20 at 22:07
I looked at another client's application event log and that excel warning (Installation of the Proof ofPurchase from the ACPI table failed. Error code ...:)is NOT there. So my only lead is gone.
– QuickBooksDev
Nov 21 at 15:16
So look at the updates that were applied to office in November, ie the 13th of November. support.microsoft.com/en-us/help/4461503/…
– Sorceri
Nov 19 at 20:31
So look at the updates that were applied to office in November, ie the 13th of November. support.microsoft.com/en-us/help/4461503/…
– Sorceri
Nov 19 at 20:31
I don't have access to my clients' machine but one told me that what was installed around that time was KB4467703 and KB4467697. Those update were not installed on my systems which are up to date. Even the client that did a system to get it working wants to get their system current again. Another client uninstalled the last 2 updates (I don't know the numbers) but didn't want to reboot for fear of updates being re-installed again.
– QuickBooksDev
Nov 20 at 22:07
I don't have access to my clients' machine but one told me that what was installed around that time was KB4467703 and KB4467697. Those update were not installed on my systems which are up to date. Even the client that did a system to get it working wants to get their system current again. Another client uninstalled the last 2 updates (I don't know the numbers) but didn't want to reboot for fear of updates being re-installed again.
– QuickBooksDev
Nov 20 at 22:07
I looked at another client's application event log and that excel warning (Installation of the Proof ofPurchase from the ACPI table failed. Error code ...:)is NOT there. So my only lead is gone.
– QuickBooksDev
Nov 21 at 15:16
I looked at another client's application event log and that excel warning (Installation of the Proof ofPurchase from the ACPI table failed. Error code ...:)is NOT there. So my only lead is gone.
– QuickBooksDev
Nov 21 at 15:16
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
We found the problem but not clear why.
As posted above our code was using a range value of
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
s = ws.Range(Ss).value
Note: that a period was used so the range was something like A1.C3
This continues to work in 7 of our 8 systems that we have seen but when we used this format in the excel screen we got a #Field! error. This is a new Excel behavior.
Changing our apps to use a colon instead of a period solved the problem.
So the range is now
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
or A1:C3
Again it worked in most systems and that cannot be explained. There was nothing in the event logs and the original posting in the header was a false alarm.
answered Nov 22 at 14:04
QuickBooksDev
53119
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
We found the problem but not clear why.
As posted above our code was using a range value of
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
s = ws.Range(Ss).value
Note: that a period was used so the range was something like A1.C3
This continues to work in 7 of our 8 systems that we have seen but when we used this format in the excel screen we got a #Field! error. This is a new Excel behavior.
Changing our apps to use a colon instead of a period solved the problem.
So the range is now
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
or A1:C3
Again it worked in most systems and that cannot be explained. There was nothing in the event logs and the original posting in the header was a false alarm.
answered Nov 22 at 14:04
QuickBooksDev
53119
add a comment |
up vote
0
down vote
We found the problem but not clear why.
As posted above our code was using a range value of
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
s = ws.Range(Ss).value
Note: that a period was used so the range was something like A1.C3
This continues to work in 7 of our 8 systems that we have seen but when we used this format in the excel screen we got a #Field! error. This is a new Excel behavior.
Changing our apps to use a colon instead of a period solved the problem.
So the range is now
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
or A1:C3
Again it worked in most systems and that cannot be explained. There was nothing in the event logs and the original posting in the header was a false alarm.
answered Nov 22 at 14:04
QuickBooksDev
53119
add a comment |
up vote
0
down vote
up vote
0
down vote
We found the problem but not clear why.
As posted above our code was using a range value of
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
s = ws.Range(Ss).value
Note: that a period was used so the range was something like A1.C3
This continues to work in 7 of our 8 systems that we have seen but when we used this format in the excel screen we got a #Field! error. This is a new Excel behavior.
Changing our apps to use a colon instead of a period solved the problem.
So the range is now
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
or A1:C3
Again it worked in most systems and that cannot be explained. There was nothing in the event logs and the original posting in the header was a false alarm.
answered Nov 22 at 14:04
QuickBooksDev
53119
We found the problem but not clear why.
As posted above our code was using a range value of
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
s = ws.Range(Ss).value
Note: that a period was used so the range was something like A1.C3
This continues to work in 7 of our 8 systems that we have seen but when we used this format in the excel screen we got a #Field! error. This is a new Excel behavior.
Changing our apps to use a colon instead of a period solved the problem.
So the range is now
Ss = "A" & Row & "." & ColNames(UsedColsSht) & Row + 1
or A1:C3
Again it worked in most systems and that cannot be explained. There was nothing in the event logs and the original posting in the header was a false alarm.
answered Nov 22 at 14:04
QuickBooksDev
53119
answered Nov 22 at 14:04
QuickBooksDev
53119
answered Nov 22 at 14:04
QuickBooksDev
53119
answered Nov 22 at 14:04
QuickBooksDev
53119
53119
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381696%2fwindows-desktop-vb-net-apps-getting-an-error-1004-0x800a03ec-reading-excel-due-t%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
So look at the updates that were applied to office in November, ie the 13th of November. support.microsoft.com/en-us/help/4461503/…
– Sorceri
Nov 19 at 20:31
I don't have access to my clients' machine but one told me that what was installed around that time was KB4467703 and KB4467697. Those update were not installed on my systems which are up to date. Even the client that did a system to get it working wants to get their system current again. Another client uninstalled the last 2 updates (I don't know the numbers) but didn't want to reboot for fear of updates being re-installed again.
– QuickBooksDev
Nov 20 at 22:07
I looked at another client's application event log and that excel warning (Installation of the Proof ofPurchase from the ACPI table failed. Error code ...:)is NOT there. So my only lead is gone.
– QuickBooksDev
Nov 21 at 15:16