What would cause a runtime error "75" in wcreports when trying to run the statistics routing.
theWhat would cause a runtime error "75" in wcreports when trying to run
statistics routing.
What is statistics routing? Runtime Error 75, is a PATH/FILE access error...
Mark
theWhat would cause a runtime error "75" in wcreports when trying to run
statistics routing.
What is statistics routing? Runtime Error 75, is a PATH/FILE access error...
Mark
Mark:
I think you provided the clue. Awhile back, before I increased my server security, a hacker somehow changed all of my public side files to read
only. I'll bet one of the files needed has a read only attribute.
I'll take a look at that right now.
Thanks Mark,
John Kidwell
On 6/27/02 10:20 AM, JOHN KIDWELL wrote to MARK BAPPE:
Mark:
I think you provided the clue. Awhile back, before I increased my server security, a hacker somehow changed all of my public side files to read only. I'll bet one of the files needed has a read only attribute.
I'll take a look at that right now.
Thanks Mark,
John Kidwell
I have to remember this more because it happens more and more. Not
hackers, but people backing up their files, like a CD, then when they RESTORE, the read-only attribute is passed on.
Could that be what happen with you rather than a hacker? I mean,
that is scary, having a hacker "enter" your system. :-)
I still have a problem with wcreports error 13 when
I try to edit the messages in wcreports.
I will figure it out after a bit.
On 6/27/02 11:39 PM, JOHN KIDWELL wrote to HECTOR SANTOS:
I still have a problem with wcreports error 13 when
I try to edit the messages in wcreports.
I will figure it out after a bit.
Thats not your problem. Thats WCREPORTS. You shouldn't get an error.
If you do, the best you can do for us is to get is a way to repeat
it. Like what is the pattern? What steps? Is it a special message
with some junk in it? Does it have an attachment? etc, etc, etc.
So if you have something concrete for us to look at, let us know
so we can fix it.
Thanks John.
Hector-
Same error 13 here, doesn't matter what msg I try to open wcreports via
any of my remote machines.
A couple of us have talked about this previously, happened after the
aup.
There were a couple of other issues in wcreports as well,
something with a couple of the ocx files.
On 6/28/02 4:50 AM, DAVE GOURD wrote to HECTOR SANTOS:
Hector-
Same error 13 here, doesn't matter what msg I try to open wcreportsvia > any of my remote machines.
Does it work on any machine?
A couple of us have talked about this previously, happened after the
aup.
But nothing that we can reproduce so its hard to find.
There were a couple of other issues in wcreports as well,
something with a couple of the ocx files.
This has been address. Just missing OCX files some people don't
have.
On 6/27/02 11:39 PM, JOHN KIDWELL wrote to HECTOR SANTOS:
I still have a problem with wcreports error 13 when
I try to edit the messages in wcreports.
I will figure it out after a bit.
Thats not your problem. Thats WCREPORTS. You shouldn't get an error.
If you do, the best you can do for us is to get is a way to repeat
it. Like what is the pattern? What steps? Is it a special message
with some junk in it? Does it have an attachment? etc, etc, etc.
So if you have something concrete for us to look at, let us know
so we can fix it.
Thanks John.
On 6/28/02 4:50 AM, DAVE GOURD wrote to HECTOR SANTOS:
Hector-
Same error 13 here, doesn't matter what msg I try to open wcreportsvia > any of my remote machines.
Does it work on any machine?
Wcreports works on all machines, but the message editing/viewing only
works on the server.
[remote1] win98se - wcreports yes but no message edit
[remote2] win98se - wcreports yes but no message edit
[remote3] win95a with all sp's upgrades - upgrade wcreports yes but no message edit
[server] winnt 4.0 wkstn sp6a - wcreports yes message edit yes
All worked on all machines/same setup previous to big aup.
A couple of us have talked about this previously, happened after the aup.
But nothing that we can reproduce so its hard to find.
There were a couple of other issues in wcreports as well,
something with a couple of the ocx files.
This has been address. Just missing OCX files some people don't
have.
We surmised that, but don't understand what happened exactly; the only changes here was the aup, nothing else. I learned this long ways back
about updates, changes, new hardware. Do one thing at a time, watch for problems.
When I am aware of AUPs, I make sure I don't change anything beforehand,
and nothing afterwards until everything checks out. The ocx thing is a non-issue though, just the error '13'.
Thank you sir...
--
D
Dave & Hector:email,
The problem persists as follows; start wcreports, message tab, private
double click on any message, run-time error "13": type mismatch, click onOK,
wcreports closes.
John
On 7/4/02 2:11 AM, DAVE GOURD wrote to HECTOR SANTOS:
On 6/28/02 4:50 AM, DAVE GOURD wrote to HECTOR SANTOS:
Hector-
Same error 13 here, doesn't matter what msg I try to open wcreportsvia > any of my remote machines.
Does it work on any machine?
Wcreports works on all machines, but the message editing/viewing only works on the server.
[remote1] win98se - wcreports yes but no message edit
[remote2] win98se - wcreports yes but no message edit
[remote3] win95a with all sp's upgrades - upgrade wcreports yes but no message edit
[server] winnt 4.0 wkstn sp6a - wcreports yes message edit yes
All worked on all machines/same setup previous to big aup.
A couple of us have talked about this previously, happened after the aup.
But nothing that we can reproduce so its hard to find.
There were a couple of other issues in wcreports as well,
something with a couple of the ocx files.
This has been address. Just missing OCX files some people don't
have.
We surmised that, but don't understand what happened exactly; the only changes here was the aup, nothing else. I learned this long ways back about updates, changes, new hardware. Do one thing at a time, watch for problems.
When I am aware of AUPs, I make sure I don't change anything beforehand, and nothing afterwards until everything checks out. The ocx thing is a non-issue though, just the error '13'.
Thank you sir...
--
D
I did a windows find for mscomctl.ocx and found it in c:\windows\system,but I
also found it in c:\program files\simple DNS plus\backup. That tells methat
the program mscomctl.ocx was backed up when I installed Simple DNS for some reason. Perhaps Simple DNS changes mscomctl.ocx and backs it up forwhatever
reason. If I could get a copy of mscomctl.ocx and copy it to my c:\windows\system directory there is a chance it will fix the problem.
Who knows,
John Kidwell
On 6/5/03 12:05 PM, JOHN KIDWELL wrote to DAVE GOURD:on
Dave & Hector:email,
The problem persists as follows; start wcreports, message tab, private
double click on any message, run-time error "13": type mismatch, click
OK,
wcreports closes.
John
On 7/4/02 2:11 AM, DAVE GOURD wrote to HECTOR SANTOS:
wcreportsOn 6/28/02 4:50 AM, DAVE GOURD wrote to HECTOR SANTOS:
Hector-
Same error 13 here, doesn't matter what msg I try to open
via > any of my remote machines.
Does it work on any machine?
Wcreports works on all machines, but the message editing/viewing only works on the server.
[remote1] win98se - wcreports yes but no message edit
[remote2] win98se - wcreports yes but no message edit
[remote3] win95a with all sp's upgrades - upgrade wcreports yes but no message edit
[server] winnt 4.0 wkstn sp6a - wcreports yes message edit yes
All worked on all machines/same setup previous to big aup.
theA couple of us have talked about this previously, happened after
onlyaup.
But nothing that we can reproduce so its hard to find.
There were a couple of other issues in wcreports as well, something with a couple of the ocx files.
This has been address. Just missing OCX files some people don't have.
We surmised that, but don't understand what happened exactly; the
forchanges here was the aup, nothing else. I learned this long ways back about updates, changes, new hardware. Do one thing at a time, watch
beforehand,problems.
When I am aware of AUPs, I make sure I don't change anything
and nothing afterwards until everything checks out. The ocx thing is a non-issue though, just the error '13'.
Thank you sir...
--
D
I did a windows find for mscomctl.ocx and found it in c:\windows\system,but I
also found it in c:\program files\simple DNS plus\backup. That tells methat
the program mscomctl.ocx was backed up when I installed Simple DNS forsome
reason. Perhaps Simple DNS changes mscomctl.ocx and backs it up forwhatever
reason. If I could get a copy of mscomctl.ocx and copy it to my c:\windows\system directory there is a chance it will fix the problem.
Who knows,
John Kidwell
On 6/5/03 12:05 PM, JOHN KIDWELL wrote to DAVE GOURD:on
Dave & Hector:email,
The problem persists as follows; start wcreports, message tab, private
double click on any message, run-time error "13": type mismatch, click
OK,
wcreports closes.
John
On 7/4/02 2:11 AM, DAVE GOURD wrote to HECTOR SANTOS:
wcreportsOn 6/28/02 4:50 AM, DAVE GOURD wrote to HECTOR SANTOS:
Hector-
Same error 13 here, doesn't matter what msg I try to open
onlyvia > any of my remote machines.
Does it work on any machine?
Wcreports works on all machines, but the message editing/viewing
noworks on the server.
[remote1] win98se - wcreports yes but no message edit
[remote2] win98se - wcreports yes but no message edit
[remote3] win95a with all sp's upgrades - upgrade wcreports yes but
message edit
[server] winnt 4.0 wkstn sp6a - wcreports yes message edit yes
All worked on all machines/same setup previous to big aup.
after theA couple of us have talked about this previously, happened
onlyaup.
But nothing that we can reproduce so its hard to find.
There were a couple of other issues in wcreports as well, something with a couple of the ocx files.
This has been address. Just missing OCX files some people don't have.
We surmised that, but don't understand what happened exactly; the
backchanges here was the aup, nothing else. I learned this long ways
forabout updates, changes, new hardware. Do one thing at a time, watch
beforehand,problems.
When I am aware of AUPs, I make sure I don't change anything
aand nothing afterwards until everything checks out. The ocx thing is
non-issue though, just the error '13'.
Thank you sir...
--
D
For Mscomctl.ocx
The date on the c:\program files\simple DNS plus\backup is 1038KB
12/9/99
The date on the c:\windows\system is 1042KB 05/22/00 John Kidwell
On 6/5/03 12:10 PM, JOHN KIDWELL wrote to JOHN KIDWELL:
I did a windows find for mscomctl.ocx and found it in c:\windows\sbut I
also found it in c:\program files\simple DNS plus\backup. That tethat
the program mscomctl.ocx was backed up when I installed Simple DNS reason. Perhaps Simple DNS changes mscomctl.ocx and backs it up forwhatever
reason. If I could get a copy of mscomctl.ocx and copy it to my c:\windows\system directory there is a chance it will fix the prob
Who knows,
John Kidwell
On 6/5/03 12:05 PM, JOHN KIDWELL wrote to DAVE GOURD:
onDave & Hector:email,
The problem persists as follows; start wcreports, message tab,
double click on any message, run-time error "13": type mismatch
OK,
wcreports closes.
John
On 7/4/02 2:11 AM, DAVE GOURD wrote to HECTOR SANTOS:
On 6/28/02 4:50 AM, DAVE GOURD wrote to HECTOR SANTOS:
Hector-
wcreportsSame error 13 here, doesn't matter what msg I try to open
via > any of my remote machines.
Does it work on any machine?
Wcreports works on all machines, but the message editing/vie
works on the server.
[remote1] win98se - wcreports yes but no message edit
[remote2] win98se - wcreports yes but no message edit
[remote3] win95a with all sp's upgrades - upgrade wcreports message edit
[server] winnt 4.0 wkstn sp6a - wcreports yes message edit yes
All worked on all machines/same setup previous to big aup.
theA couple of us have talked about this previously, happe
aup.
But nothing that we can reproduce so its hard to find.
There were a couple of other issues in wcreports as well, something with a couple of the ocx files.
This has been address. Just missing OCX files some peopl
have.
onlyWe surmised that, but don't understand what happened exactly
forchanges here was the aup, nothing else. I learned this long
about updates, changes, new hardware. Do one thing at a time
problems.
beforehand,When I am aware of AUPs, I make sure I don't change anything
and nothing afterwards until everything checks out. The ocx non-issue though, just the error '13'.
Thank you sir...
--
D
Hi John,
Only one occurrence of it here-
file date 05/22/00
file size 1042 kb
file vers 6.00.8862
I have just gotten used to using wcreports on the server instead of
across the lan.
--
D
For Mscomctl.ocx
The date on the c:\program files\simple DNS plus\backup is 1038KB 12/9/99
The date on the c:\windows\system is 1042KB 05/22/00 John Kidwell
On 6/5/03 12:10 PM, JOHN KIDWELL wrote to JOHN KIDWELL:
I did a windows find for mscomctl.ocx and found it in c:\windows\sbut I
also found it in c:\program files\simple DNS plus\backup. That tethat
the program mscomctl.ocx was backed up when I installed Simple DNS reason. Perhaps Simple DNS changes mscomctl.ocx and backs it up forwhatever
reason. If I could get a copy of mscomctl.ocx and copy it to my c:\windows\system directory there is a chance it will fix the prob
Who knows,
John Kidwell
On 6/5/03 12:05 PM, JOHN KIDWELL wrote to DAVE GOURD:
onDave & Hector:email,
The problem persists as follows; start wcreports, message tab,
double click on any message, run-time error "13": type mismatch
OK,
wcreports closes.
John
On 7/4/02 2:11 AM, DAVE GOURD wrote to HECTOR SANTOS:
On 6/28/02 4:50 AM, DAVE GOURD wrote to HECTOR SANTOS:
Hector-
wcreportsSame error 13 here, doesn't matter what msg I try to open
via > any of my remote machines.
Does it work on any machine?
Wcreports works on all machines, but the message editing/vie works on the server.
[remote1] win98se - wcreports yes but no message edit
[remote2] win98se - wcreports yes but no message edit
[remote3] win95a with all sp's upgrades - upgrade wcreports message edit
[server] winnt 4.0 wkstn sp6a - wcreports yes message edit yes
All worked on all machines/same setup previous to big aup.
theA couple of us have talked about this previously, happe
aup.
But nothing that we can reproduce so its hard to find.
There were a couple of other issues in wcreports as well, something with a couple of the ocx files.
This has been address. Just missing OCX files some peopl have.
onlyWe surmised that, but don't understand what happened exactly
forchanges here was the aup, nothing else. I learned this long about updates, changes, new hardware. Do one thing at a time
problems.
beforehand,When I am aware of AUPs, I make sure I don't change anything
and nothing afterwards until everything checks out. The ocx non-issue though, just the error '13'.
Thank you sir...
--
D
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 198:20:14 |
| Calls: | 2,007 |
| Calls today: | 4 |
| Files: | 11,114 |
| Messages: | 942,429 |