Y
Yony Goldblat
Hi there,
We recently upgraded our systems to a much faster server.
Only the hardware changed, and a fresh installation of
Windows 2000 server was done on the new system.
We transferred the entire intranet to the new server, but
then we found out that a primary service is not working.
This service brings secured documents from a directory on
the server.
This application worked 100% fine on the old server but
on the new server it seems to be "randomly" working.
The application is taken from a Microsoft site (it's a
simple adodb.stream which sends a binary file to the
client) and since it worked fine on the old server we
assume that it is not a programming error.
The error messages it gives us are randomly displayed -
pressing the Refresh key brings every time a different
error message, and sometimes opens the document with no
problems. Again, it seems randomally! Here are the 2
error messages:
1)
Provider (0x8007000E)
Not enough storage is available to complete this
operation.
2)
ADODB.Stream (0x800A0BBA)
File could not be opened.
We have lots of free space on the HD (about 100GB) and
lots of free memory.
My guess is that windows has some kind of cache where it
stores files which are going to be binary sent by stream,
then these files are filling this cache/buffer up to
it's capacity. I haven't found any documentation about
it, so it's just a guess.
Does anyone have any idea how to solve this weird problem?
Thanks,
Yony Goldblat
IT Developer
Philips Medical Systems
We recently upgraded our systems to a much faster server.
Only the hardware changed, and a fresh installation of
Windows 2000 server was done on the new system.
We transferred the entire intranet to the new server, but
then we found out that a primary service is not working.
This service brings secured documents from a directory on
the server.
This application worked 100% fine on the old server but
on the new server it seems to be "randomly" working.
The application is taken from a Microsoft site (it's a
simple adodb.stream which sends a binary file to the
client) and since it worked fine on the old server we
assume that it is not a programming error.
The error messages it gives us are randomly displayed -
pressing the Refresh key brings every time a different
error message, and sometimes opens the document with no
problems. Again, it seems randomally! Here are the 2
error messages:
1)
Provider (0x8007000E)
Not enough storage is available to complete this
operation.
2)
ADODB.Stream (0x800A0BBA)
File could not be opened.
We have lots of free space on the HD (about 100GB) and
lots of free memory.
My guess is that windows has some kind of cache where it
stores files which are going to be binary sent by stream,
then these files are filling this cache/buffer up to
it's capacity. I haven't found any documentation about
it, so it's just a guess.
Does anyone have any idea how to solve this weird problem?
Thanks,
Yony Goldblat
IT Developer
Philips Medical Systems