Copy error 80004005 on Windows Server 2003

[Jeff Curren]

The following works on XP and Windows 2000 but the .Copy method fails on
Windows Server 2003. Can it be made to run on Windows Server 2003?

dim objSpreadsheet
set objSpreadsheet = CreateObject("OWC11.Spreadsheet")
objSpreadsheet.Cells(1, 1).Value = "A1 initial value"
objSpreadsheet.Cells(1, 2).Value = "B1 initial value"

dim rngDest
set rngDest = objSpreadsheet.Range("B1")

objSpreadsheet.Range("A1:A1").Copy rngDest

Jeff

 

[Guest]

are you sure that this can't be resolved by something simpler?

like for example-- do you have office on the 2000/xp box; but you don't have
it on the 2003 box?

or for example-- this is important-- are you trying to get this workin on
2003 web edition?

i don't know for sure, but there are certain APPLICATIONS that you can't run
on 2003 web edition; SQL Server (even just the client) is one of them

i think that OWC might be the same way.. i dont know for sure

but i hope i helped a lil

 

[Jeff Curren]

Simpler than what? You are the first to offer any suggestions at all. And
THANK YOU for that!

We're not running web editions of anything; only full-blown everything. The
sample I published is so simply, I am really trying to find out if anyone in
the world has ever run the OWC Copy function on a Windows 2003 server.

To the best of our knowledge, we have installed only the OWC components on
both 2000 and 2003 servers. However, on one Windows 2003 server, we did
install Excel and the OWC Copy function still fails.

 

[Josh Sale]

Jeff,

Did you ever make any progress on this? We're having the same problem doing
a Copy on a range (although in our case we haven't supplied the destination
argument). Like you, our code works on 2000 and XP but fails on Windows
Server 2003. We're running OWC 11.

In our case, we're getting error -2147467529.

If I look at the range before I do the Copy (e.g., inspect its .Address
property), the range looks just fine.

Hope you've made some break through that you can share!

TIA,

josh

 

[Jeff Curren]

No progress. I thought Microsoft would be interested if OWC11 fails on
Windows Server 2003 but apparently I was wrong.

 

[Alvin Bruney [MVP]]

ok, i'm a sucker for a challenge. Can you provide a small but complete
program that demonstrates the issue. Small but complete programs are defined
here (http://www.yoda.arachsys.com/csharp/complete.html)

--
Regards,
Alvin Bruney [Microsoft MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://www.lulu.com/owc

 

[Josh Sale]

We produced a little program that demonstrates the problem and submitted it
to Microsoft. They've reproduced the problem and are looking into it.

Their initial take was that this was a security thing associated with
protecting the clipboard.

If you want I can get my colleague to ship you a copy of the test case.

josh

ok, i'm a sucker for a challenge. Can you provide a small but complete
program that demonstrates the issue. Small but complete programs are
defined here (http://www.yoda.arachsys.com/csharp/complete.html)

--
Regards,
Alvin Bruney [Microsoft MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://www.lulu.com/owc
----------------------------------------------------------

No progress. I thought Microsoft would be interested if OWC11 fails on
Windows Server 2003 but apparently I was wrong.

 

[Alvin Bruney [MVP]]

The developers at Microsoft are very capable of solving the problem. Thanks.

--
Regards,
Alvin Bruney [Microsoft MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://www.lulu.com/owc
----------------------------------------------------------

We produced a little program that demonstrates the problem and submitted
it to Microsoft. They've reproduced the problem and are looking into it.

Their initial take was that this was a security thing associated with
protecting the clipboard.

If you want I can get my colleague to ship you a copy of the test case.

josh

ok, i'm a sucker for a challenge. Can you provide a small but complete
program that demonstrates the issue. Small but complete programs are
defined here (http://www.yoda.arachsys.com/csharp/complete.html)

--
Regards,
Alvin Bruney [Microsoft MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://www.lulu.com/owc
----------------------------------------------------------

No progress. I thought Microsoft would be interested if OWC11 fails on
Windows Server 2003 but apparently I was wrong.

:

Jeff,

Did you ever make any progress on this? We're having the same problem
doing
a Copy on a range (although in our case we haven't supplied the
destination
argument). Like you, our code works on 2000 and XP but fails on
Windows
Server 2003. We're running OWC 11.

In our case, we're getting error -2147467529.

If I look at the range before I do the Copy (e.g., inspect its .Address
property), the range looks just fine.

Hope you've made some break through that you can share!

TIA,

josh

 

[Jeff Curren]

Thanks Alvin.

My original post contains a small and complete program that demonstrates the
issue.

Do you have a question regarding how to reproduce it? Please let me know if
so.

Jeff

 

[Alvin Bruney [MVP]]

Well i thought you had submitted this to MS support so I didn't continue
looking at it. If you haven't I can submit it directly to them on your
behalf otherwise, I'll just wait on what they say.

--
Regards,
Alvin Bruney [Microsoft MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://www.lulu.com/owc
----------------------------------------------------------

Thanks Alvin.

My original post contains a small and complete program that demonstrates
the
issue.

Do you have a question regarding how to reproduce it? Please let me know
if
so.

Jeff

 

[Nick Palmer]

Alvin,

I'm Josh's colleague. I have submitted this to Microsoft and I'm working
with developer support to track down the problem. Once I found out the
answer (hopefully) I'll post it here. Last I heard, they were tracing thru
the guts of OWC and trying to figure out a security problem with the
clipboard.

Nick

Well i thought you had submitted this to MS support so I didn't continue
looking at it. If you haven't I can submit it directly to them on your
behalf otherwise, I'll just wait on what they say.

--
Regards,
Alvin Bruney [Microsoft MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://www.lulu.com/owc