Date time assert error in a slick-c module...

[photex]

Howdy folks,

On Linux as well as OSX my instances of slickedit just threw up a slick-c error panel and disappeared... probably 5 minutes apart from each other. I'm unable to run either now as I get the same assertion failure for : "validDate(year, month, day)" in file DateTime.e on line 148

[davehohl]

Same thing happened to me a few minutes ago on my Windows machine.  I cannot run SlickEdit any more either.

[photex]

Yikes ok then... HotFix please!

[davehohl]

Maybe this is how they get everyone to try the new Beta version!   

[photex]

I'm picturing the Slickedit development offices to be a rather busy scene at the moment.

But yeah... back to the beta. haha

[davehohl]

Turns out this is happening on the Beta version also.  Check that board for more info.

[JeffB]

Ditto.

Happened (I think) at precisely 7pm EST for me...can't start SlickEdit at all...not good for my deadlines tonight!

I was going to install the Beta, but it sounds like that won't work either.

[csrajput]

I am running SlickEdit v15 on Windows XP 32bit. SlickEdit was running and I went out for some time. When I came back I saw the very same error. I tried restarting it several times, but did not help. Checked SlickEdit forums and found that many people are having this problem today, so took a simple guess that its failing because of the date (remember the Y2K). I just tried to change the system date to 03/02/2011 and started slickedit. It started without any problem. Then I changed the system date back to today's date and restarted slick edit. It still works. I restarted it several times and it is still working. If it doesnt work after you reset the date back to today's date, then I would suggest to use tomorrows date at least for today if you are keen on working on SlickEdit today

Donno what the problem could be... Sad

Try this and let us know if it works.

- Charan

[jamiehankins]

Wow, whoever hard-coded whatever gummed this up really knows how to make friends and influence people!

[jamiehankins]

Sure enough, setting time forward by a day, starting vs, then setting back fixes the problem, at least for now.

[JeffB]

yep...worked for me   +1 HP

[LBCEi]

Same thing for me.

Glad I wasn't needing to using SE today.

Looks like we have been bitten by the Y2K + 11 years, 60 days bug.

Les

[Ding Zhaojie]

I removed the ASSERT in Datetime.e to make SE run. Waiting for the final hotfix.

[Rodney]

I have attached a fixed se/datetime/DateTime.e module that should fix this for all. Beta users can also use this file since it is exactly the same between versions.

0a. Temporarily move your system time forward in time by 1 day, or
0b. If you do not have permissions to change your system time, delete your state file in your config-dir, which may give you enough time to load the offending module before the error*
1a. Backup your existing macros/se/datetime/DateTime.e and replace with attached, or
1b. If you do not have permissions to replace the file, put the file in some location you do have write permissions (Desktop).
2. Load the new DateTime.e from Macro>Load Module, or

*Where is my config directory?
Windows default for v15.0.1: .../Documents/My SlickEdit Config/15.0.1/
UNIX default for v15.0.1: $HOME/.slickedit/15.0.1/

We will roll this into a hotfix ASAP. Thanks!

--rodney

[microcode]

2. Load from Macro>Load Module

How do I run Macro>Load Module?  After I click OK on the assertion error box, SE closes!  I can't do anything within SE because of the assertion error. (Mac OSX, SE v15.0.1)

Is there a way to compile the new DateTime.e from the command line or something?

EDIT: I was able to get SE to launch by deleting the vslick.stu and vrestore.slk files from my config directory (after making backups first, of course.) I don't know which file (or both) actually needed to be deleted.

However, I still wasn't able to load the new DateTime.e macro because the Mac OS file selection dialog box doesn't let me descend into the SlickEditV1501.app directory! Thank you, Apple!  So I put the DateTime.e file on my Desktop, and told SE to load it from there.