| « Security Certificate expiration in Lotus Domino on May 18th 2009 | Blog is back » |
The 8.5 designer....
.. and myself, we just cant get along.

I need to get trusty old killnotes to get rid of the hanging designer client because it won't shutdown. If there's any feature I really don't like about 8.5, it's got to be the Designer client. It. Just. Doesn't. Work.
Update 07-05-2009:
I've decided to create a PMR anyway. Keep you posted.

I need to get trusty old killnotes to get rid of the hanging designer client because it won't shutdown. If there's any feature I really don't like about 8.5, it's got to be the Designer client. It. Just. Doesn't. Work.
Update 07-05-2009:
I've decided to create a PMR anyway. Keep you posted.
11 comments
Comment from: Piyush [Visitor]
Could you please share more details on this like what you doing when you get these errors ? is it always coming ?
By the way, Designer 851 will have all your problems solved :-)
By the way, Designer 851 will have all your problems solved :-)
05/05/09 @ 09:32
Hi Piyush
This is a new error that I can't reproduce, but it has been coming up over the past couple of days. What I really like is the explanation on the errors "Error".
Can't wait for the 8.5.1 designer.
This is a new error that I can't reproduce, but it has been coming up over the past couple of days. What I really like is the explanation on the errors "Error".
Can't wait for the 8.5.1 designer.
05/05/09 @ 09:43
Comment from: sean cull [Visitor] · http://www.seancull.co.uk
see here for a better way to restart the client using nsd
cheers sean
http://seancull.co.uk/Public/seancull.nsf/dx/restarting-notes-cleanly.htm?opendocument&comments#anc1
cheers sean
http://seancull.co.uk/Public/seancull.nsf/dx/restarting-notes-cleanly.htm?opendocument&comments#anc1
05/05/09 @ 09:50
HI Sean
I know about the NSD -kill, but Killnotes does the job fine for me. I didn't want to create a pmr for this, so I use killnotes.
I know about the NSD -kill, but Killnotes does the job fine for me. I didn't want to create a pmr for this, so I use killnotes.
05/05/09 @ 10:33
Comment from: Ralf M Petter [Visitor]
You should do what the error say and have a look in the error log. The stack trace there will give you some hints to further analyze the problem.
05/05/09 @ 13:50
Comment from: Piyush [Visitor]
Agreed, error description should be correct & more user friendly.
"An error has occured. See log for more details" is the catch ;-)
"An error has occured. See log for more details" is the catch ;-)
05/05/09 @ 14:09
Comment from: Simon O'Doherty [Visitor]
If you are able to open a PMR you should (even if you don't want a resolution at this time). That way development can track it.
At a guess a widget is being sent a message when it has already been shut down. Why. Not sure.
This is what I use for killing notes.
>type killnotes.cmd
@echo off
taskkill /F /FI "IMAGENAME eq nsd.exe"
taskkill /F /FI "IMAGENAME eq notes2.exe"
taskkill /F /FI "IMAGENAME eq nlnotes.exe"
taskkill /F /FI "IMAGENAME eq notes.exe"
taskkill /F /FI "IMAGENAME eq ntaskldr.EXE"
At a guess a widget is being sent a message when it has already been shut down. Why. Not sure.
This is what I use for killing notes.
>type killnotes.cmd
@echo off
taskkill /F /FI "IMAGENAME eq nsd.exe"
taskkill /F /FI "IMAGENAME eq notes2.exe"
taskkill /F /FI "IMAGENAME eq nlnotes.exe"
taskkill /F /FI "IMAGENAME eq notes.exe"
taskkill /F /FI "IMAGENAME eq ntaskldr.EXE"
05/05/09 @ 14:39
Yeah well, I've enabled all client debugging, so if it occurs again I'll see if I can find it. The local log.nsf has no more info, but I'll nsd the client next time too, so maybe I'll be able to find out what's up.
05/05/09 @ 14:59
I was running LND 8.5 with the Sametime connect client 8.0. Shutting down Sametime seems to have resolved the issue for me.
06/05/09 @ 20:34
Hi Michael,
I'm allready using the embedded client, but thanks for the tip
I'm allready using the embedded client, but thanks for the tip
06/06/09 @ 10:18