I searched for this but didn't come up with anything. This is the second time it has happened and it seems to do it after running for a few hours. I'm not doing anything with the program and usually am online browsing when this window pops up.
I have to do the Ctrl-Alt-Delete to get out of it.
Value can not be Null error
- stan_qaz
- Omniscient Kiwi
- Location: Gilbert, Arizona
Post
Re: Value can not be Null error
If you can send a set of logs to firetrust, put in a link to this post and use chris as the ticket number. They are a bit busy down there (see earthquake topic) but he should get back to you on the problem.
I am not a Firetrust employee just a MW user.
--
First rule of computer consulting: Sell a customer a Linux computer and you'll eat for a day,
sell a customer a Windows computer and you'll eat for a lifetime.
--
First rule of computer consulting: Sell a customer a Linux computer and you'll eat for a day,
sell a customer a Windows computer and you'll eat for a lifetime.
- TopThumb
- Student Sheep
Post
Re: Value can not be Null error
I tried sending a the error log but it keeps failing to send for some reason and I did put chris in there.
- stan_qaz
- Omniscient Kiwi
- Location: Gilbert, Arizona
Post
Re: Value can not be Null error
Hang around and he'll be by, there is an alternate method of getting him your data that he can give you.
I am not a Firetrust employee just a MW user.
--
First rule of computer consulting: Sell a customer a Linux computer and you'll eat for a day,
sell a customer a Windows computer and you'll eat for a lifetime.
--
First rule of computer consulting: Sell a customer a Linux computer and you'll eat for a day,
sell a customer a Windows computer and you'll eat for a lifetime.
- TopThumb
- Student Sheep
Post
Re: Value can not be Null error
I emailed him the file and link this time.
Thanks for your help though.
Thanks for your help though.
-
ru
Post
Re: Value can not be Null error
Great. I did get the logs when they were sent, your main server is rejecting sending them as you've got a typo in the email address field for that account, so MailWasher then tried to send through the Firetrust server which worked fine.
As for the error, it would seem like it's being caused when MailWasher routinely cleans up the Event Log, so on the list to be fixed by programmer.
As for the error, it would seem like it's being caused when MailWasher routinely cleans up the Event Log, so on the list to be fixed by programmer.