SPS224G4 crash on show run when features enables over SNMP

Hi.
I got SPS224G4 switch, on which I enable LLDP protocol over SNMP (using snmpset).
Now I can't do "show run" in cli - it crashes, then reboots:
How to replicate:
console# delete startup-config
<reboot>
console# conf term
console(config)# snmp-server enable
console(config)# snmp-server community secret1 rw
console(config)# exit
console# write
>snmpset -v2c -c secret1 <switch_ip> 1.3.6.1.4.1.3955.89.110.1.1.1.0 i 1
CISCOSB-LLDP-MIB::rlLldpEnabled.0 = INTEGER: true(1)
console# show run
interface range ethernet e(1-24)
shutdown
exit
No18-Nov-2008 12:41:40 %SYSLOG-F-OSFATAL:
FATAL ERROR: STSA: ABORT DATA exception
***** FATAL ERROR *****
SW Version : 1.0.2.23
Version Date: 18-Nov-2008
Version Time: 12:38:16
Instruction 0x4D98F8
Exception vector 0x10
Program state register 0x60000013
***************** SYSTEM RESET *****************

Hi,
"It would be nice of you if you can point me something where LLDP is officialy supported."
The new Sx300 series switches support LLDP and as of the new firmware release (approx release May/June 2011) it will also support Textview (CLI) like the SPS switches amongst other features like CDP and Smartports.
For an overview of the Sx300 series switches, please visit the page below :
http://www.cisco.com/en/US/partner/prod/collateral/switches/ps5718/ps10898/qa_c67-618260.html
Does this seem like a switch that can meet up to your requirements ? Please feel free if you would have any additional questions.
Best regards,
Nico Muselle
Sr. Network Engineer - CCNA
Cisco Sofia STAC

Similar Messages

What is the name of the tooltips that shows up when you hover over a UIbutton?, such as "back", "foreward", "home" etc

Okey so basically I've themes my windows 7 into a black state.
The thing about that is that the default font color firefox uses for tooltips and other information is back so its quite impossible for me to read.
After a while googleing I found out that something called userChrome.css can be used so naturally I looked furhter.
I found answers for almost everything I was looking for, except these "button tooltips".
Heres my userChrome.css code:
menubar, menu {
color: black !important;
menupopup > menu,
menupopup > menuitem,
popup > menu,
popup > menuitem {
color: white !important;
tooltip, statusbar {
color: white !important;
Basically it takes care of all text that was black and turns it the way I like it.
So what is the name of the tooltips that shows up when you hover over a UIbutton? such as "back"
With the correct name I should be able to add
name {
color: white !important
and it should work just fine :)

hey 88_King,
go to http://support.lenovo.com and download any one or all the software you require from here.
and most of the items you need is under ThinkVantage
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

Firefox gets stuck, crashes, and continues running when closed.

I have to reload pages quite frequently because Firefox just stops or crashes. It also continues running in the background even though I've closed it.
Also popping up is "about:blank" in the middle of loading a new page. I have excellent malware programs and have no problems with IE.
I want to reload Firefox 3.5...... Please advise the best way to do this.

Don't worry , I can't type.
There is a Capital on "Profiles" and it should read that Firefox is running but does not show up in the processes running list

Default Keyboard showing up when not enabled

Afternoon all,
First off my iPhone is a 5C running iOS 8.0.2
I recently downloaded the Swiftkey keyboard and loved it enough to remove my default English keyboard on my iPhone. So I ran into a problem when I did this though. Whenever I switched out of my Messages app and switched back the Emoji keyboard would be set to default in place of swiftkey. I had already changed the order preference under settings to have swiftkey as the first keyboard but this kept happening, enough times where I just removed the Emoji keyboard all together so just swiftkey was left. Now the problem I am running into is that the default iOS keyboard is now popping up whenever I open the app, even though it is not set as one of my keyboards. I am able to get the custom keyboard back by closing the app and opening up again. What's the point of setting a default keyboard if the OS is just going to override it at the start anyway? Any idea if there is an easy fix or is this some bug that will have to get patched in the future?
Thanks!

I think I may have put iPhoto in HHS trash. Could that be the problem?
I don't know what "HHS trash" is. If you put the iPhoto app into the trash on the Dock and emptied it, that would prevent you from opening iPhoto until it was reinstalled, of course, but it wouldn't affect your photos.
You didn't answer my question, though. Do you have backups? Is your computer actually 7 years old, and has it ever had the hard drive replaced?

Show image when cursor hovers over image

I would like to have the "i" image used to flip to the information screen be hidden or invisible unless the user hovers over the image, where I want the image to be visible and active after a second or two delay. This will allow a click or touch in the image area without activating the screen change.
I've seen one or two iPhone apps which appear to do this, only showing the image when it is activated and otherwise the normal program image is visible and active. So, I know that it is possible. I'm just too new to objective C and the iphone SDK to know how to do it myself just yet.
The standard utility app template which comes with the flipView controller and the "i" in the mainView appears to be always on. I'm sure there is a way to use view.hidden to hide and show it, but am not sure how to detect a hover then a touch, rather than just a touch.
Any examples showing this would be appreciated.
Thanks

Some progress on this, but still working on it. I attempted to take the Utility Application template, and then add a subview to draw the layer with my own images. Somehow I don't seem to be able to get my new drawing to display. Instead I get a completely black view which also obscures the original view loaded from the nib.
Can anyone tell me what I'm doing wrong?
First, I take a blank Utility Application template, which shows the dark gray screen with the little information icon in the lower right corner.
Next, add 2 class files which (1. Scenes.m) defines my sceneFiles and scenes structure which reads in my sceneFile.plist data into a dictionary structure so I can design my own layouts, and (2. Pieces.m) defines my board pieces, translation tables, and an image dictionary currently composed of PNG images read from individual files.
Next, add code to MainViewController.m to initialize my view:
@implementation MainViewController
- (id)initWithNibName:(NSString *)nibNameOrNil bundle:(NSBundle *)nibBundleOrNil {
if (self = [super initWithNibName:nibNameOrNil bundle:nibBundleOrNil]) {
// Custom initialization
return self;
- (void)viewDidLoad {
UIView* mainView = [[MainView alloc] initWithFrame:CGRectMake(0, 0, 480, 320)];
[self.view addSubview:mainView];
[mainView release];
Now, in MainView.m I draw my view:
- (id)initWithFrame:(CGRect)frame {
if (self = [super initWithFrame:frame]) {
// Initialization code
myPieces = [[Pieces alloc] init]; // setup piece images and index tables
myScenes = [[Scenes alloc] init]; // read in scene file(s)
sceneIndex = 0;
currentSceneKey = [myScenes.sceneKeys objectAtIndex:sceneIndex];
// begin drawing
NSDictionary* myScene = [myScenes.scenes objectForKey:currentSceneKey];
if (myScene) {
NSString* sceneTitle = [myScene objectForKey:@"Title"];
NSString* sceneTableau = [myScene objectForKey:@"Tableau"];
for (int i=0; i<boardWidth; i++) {
for (int j=0; j<boardHeight; j++) {
NSRange myRange=NSMakeRange(((jboardWidth)+i)3,2);
NSString* imgKey = [sceneTableau substringWithRange:myRange];
NSString* newKey = [myPieces.backgrounds objectForKey:imgKey];
UIImage* img=[myPieces.figures objectForKey:newKey]; // get image
[img drawAtPoint:CGPointMake(i*cellSize, j*cellSize)];
UIImage* title = [UIImage imageNamed:sceneTitle];
[title drawAtPoint:CGPointMake(0,288)];
[title release];
} // if myScene
// end drawing
return self;
Initially, the code between the "begin drawing" and "end drawing" was in the "drawRect" method, but it didn't seem to be doing anything, so I moved it to test it, and there was no apparent difference. I did put NSLog statements in drawRect and initWithFrame, and the code is being called. My images just aren't displaying.
FYI
// Scenes.h
#import <Foundation/Foundation.h>
#define boardWidth 15
#define boardHeight 9
#define cellSize 32
@interface Scenes : NSObject {
NSMutableArray* sceneFiles;
NSMutableDictionary* scenes;
NSMutableArray* sceneKeys;
-(id)init;
@property (nonatomic, retain) NSMutableArray* sceneFiles;
@property (nonatomic, retain) NSMutableDictionary* scenes;
@property (nonatomic, retain) NSMutableArray* sceneKeys;
@end
// Pieces.h
#import <Foundation/Foundation.h>
@interface Pieces : NSObject {
NSMutableDictionary* figures;
NSMutableDictionary* actions;
NSMutableDictionary* backgrounds;
NSMutableDictionary* foregrounds;
-(id)init;
@property (nonatomic, retain) NSMutableDictionary* figures;
@property (nonatomic, retain) NSMutableDictionary* actions;
@property (nonatomic, retain) NSMutableDictionary* backgrounds;
@property (nonatomic, retain) NSMutableDictionary* foregrounds;
@end
I know that the initialization of the arrays and dictionaries in Scenes and Pieces is working correctly as well placed NSLog statements in the init routines display the proper text. The code is working in an OpenGLES template that was a hodgepodge of test cases, and now I'm trying to put the pieces together in a preperly designed project, and I'm getting a black sceen.
The other project has a "myContext" variable, but as it was copied from some example code, I'm not sure how it is actually used, as most places the sample code was setting it to nil, and only one place at the beginning of drawRect, it was set to " UIGraphicsGetCurrentContext()". I've tried my code both with this and without it, and there does not appear to be any difference.

JavaScript menu is not showing up, when it comes over applet area, why?

When my javascript menu is overlapping on applet, the menu is going behind the applet. Is there any solution to get rid this. Please, anybody have the solution mail me at this id.
[email protected]
thanks
sateesh

Many people have tried to solve this problem but just about the only thing you can do is to put your applet in a <DIV> or <LAYER> (depending on the browser you want to support) and turn the <DIV> or <LAYER> invisible when your menu is activated. You'll find that your menu will also be displayed behind a FORM and other heavy-weight component, not just an applet!
Good luck!
V.V.

Router Crashes after entering "show run" or similar commands

Hello,
Im having a problem with my Company router C3845-ADVSECURITYK9-M, software Version 15.1(4)M. After i issue "show run" it tends to crash in middle of output, router restarts itself to be precise....same thing happened when i tried "show stack" afterwards, it happened several times when trying to show running config, so im guessing it has some problem when trying to display large outputs...i have never heard of such thing though so im asking for advice,
These are some informations i gathered:
show version:....
System returned to ROM by error - a Software forced crash, PC 0x60AD4710 at 14:10:56 CET-SUM Wed Aug 13 2014
xxxx#sh env
SYS PS1 is present.
Fan status: Normal
Input Voltage status: Normal
DC Output Voltage status: Normal
Type: AC
Thermal status: Normal
SYS PS2 is absent.
AUX(-48V) PS1 is absent.
AUX(-48V) PS2 is absent.
Fan 1 OK
Fan 2 OK
Fan 3 OK
Fan Speed Setting: Normal
Alert settings:
Intake temperature warning: Enabled, Threshold: 55
Core temperature warning: Enabled, Threshold: 70 (CPU: 90)
Board Temperature: Normal
Internal-ambient temperature = 38, Normal
CPU temperature = 50, Normal
Intake temperature = 32, Normal
Backplane temperature = 29, Normal
Voltage 1(3300) is Normal, Current voltage = 3284 mV
Voltage 2(5150) is Normal, Current voltage = 5153 mV
Voltage 3(2500) is Normal, Current voltage = 2525 mV
Voltage 4(1200) is Normal, Current voltage = 1203 mV
xxxx#sh logg
Syslog logging: enabled (0 messages dropped, 120 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 62 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 178 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 181 message lines logged
Logging to 10.254.0.49 (udp port 514, audit disabled,
link up),
181 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Logging to 10.254.8.44 (udp port 514, audit disabled,
link up),
181 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Log Buffer (1000000 bytes):
*Aug 13 12:33:24.867: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Initialized
*Aug 13 12:33:24.871: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Enabled
*Aug 13 12:33:25.635: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
*Aug 13 12:33:25.635: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to reset
*Aug 13 12:33:25.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface Onboard VPN, changed state to up
*Aug 13 12:33:26.635: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Aug 13 12:33:26.635: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Aug 13 12:33:27.787: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Aug 13 12:33:27.787: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Aug 13 13:33:29.023: %SYS-6-CLOCKUPDATE: System clock has been updated from 12:33:29 UTC Wed Aug 13 2014 to 13:33:29 MET Wed Aug 13 2014, configured from console by console.
*Aug 13 14:33:29.023: %SYS-6-CLOCKUPDATE: System clock has been updated from 13:33:29 MET Wed Aug 13 2014 to 14:33:29 CET-SUM Wed Aug 13 2014, configured from console by console.
*Aug 13 14:33:30.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:0, changed state to down
*Aug 13 14:33:30.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:1, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:2, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:3, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:4, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:5, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:6, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:7, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:8, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:9, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:10, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:11, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:12, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:13, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:14, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:16, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:17, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:18, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:19, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:20, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:21, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:22, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:23, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:24, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:25, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:26, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:27, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:28, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:29, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:30, changed state to down
*Aug 13 14:33:30.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:15, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:0, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:1, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:2, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:3, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:4, changed state to down
*Aug 13 14:33:30.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:5, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:6, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:7, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:8, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:9, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:10, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:11, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:12, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:13, changed state to down
*Aug 13 14:33:30.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:14, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:16, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:17, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:18, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:19, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:20, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:21, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:22, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:23, changed state to down
*Aug 13 14:33:30.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:24, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:25, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:26, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:27, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:28, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:29, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:30, changed state to down
*Aug 13 14:33:30.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1:15, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:0, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:1, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:2, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:3, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:4, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:5, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:6, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:7, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:8, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:9, changed state to down
*Aug 13 14:33:30.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:10, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:11, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:12, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:13, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:14, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:16, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:17, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:18, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:19, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:20, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:21, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:22, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:23, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:24, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:25, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:26, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:27, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:28, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:29, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:30, changed state to down
*Aug 13 14:33:30.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/1:15, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:0, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:1, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:2, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:3, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:4, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:5, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:6, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:7, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:8, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:9, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:10, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:11, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:12, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:13, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:14, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:16, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:17, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:18, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:19, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:20, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:21, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:22, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:23, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:24, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:25, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:26, changed state to down
*Aug 13 14:33:30.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:27, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:28, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:29, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:30, changed state to down
*Aug 13 14:33:30.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0:15, changed state to down
*Aug 13 14:33:30.731: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
*Aug 13 14:33:31.535: %LINK-3-UPDOWN: Interface Serial0/1/0:1, changed state to down
*Aug 13 14:33:31.795: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
*Aug 13 14:33:31.999: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to reset
*Aug 13 14:33:32.599: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1/0:1, changed state to down
*Aug 13 14:33:32.799: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down
*Aug 13 14:33:32.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
*Aug 13 14:33:34.811: %QOS_CLI_DEPRECATE-4-MAX_RESERVED_BW: max-reserved-bandwidth on interface has been deprecated. For further information, please consult Product Bulletin 580832, Legacy QoS CLI Commands Deprecation
*Aug 13 14:33:34.815: Interface Serial0/1/0:1 max_reserved_bandwidth config will not
take effect on the queueing features configured via service-policy
*Aug 13 14:33:35.795: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
*Aug 13 14:33:35.795: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Aug 13 14:33:36.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
*Aug 13 14:33:36.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Aug 13 14:33:36.811: %LINK-5-CHANGED: Interface Serial0/1/0:1, changed state to administratively down
*Aug 13 14:33:37.419: %LINK-5-CHANGED: Interface Dialer1, changed state to administratively down
*Aug 13 14:33:38.055: %SYS-5-CONFIG_I: Configured from memory by console
*Aug 13 14:33:38.491: %SYS-5-RESTART: System restarted --
Cisco IOS Software, 3800 Software (C3845-ADVSECURITYK9-M), Version 15.1(4)M, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 24-Mar-11 17:29 by prod_rel_team
*Aug 13 14:33:38.495: %SNMP-5-COLDSTART: SNMP agent on host xxxx is undergoing a cold start
*Aug 13 14:33:38.519: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Aug 13 14:33:38.699: %SYS-6-BOOTTIME: Time taken to reboot after reload = 158 seconds
*Aug 13 14:33:38.859: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up
*Aug 13 14:33:38.867: %CONTROLLER-5-UPDOWN: Controller E1 0/0/1, changed state to up
*Aug 13 14:33:38.875: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.875: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Aug 13 14:33:38.879: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON
*Aug 13 14:33:38.896: %CONTROLLER-5-UPDOWN: Controller E1 1/0, changed state to up
*Aug 13 14:33:39.140: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.254.0.49 port 514 started - CLI initiated
*Aug 13 14:33:39.140: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.254.8.44 port 514 started - CLI initiated
*Aug 13 14:33:40.860: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to up
*Aug 13 14:33:40.868: %LINK-3-UPDOWN: Interface Serial0/0/1:15, changed state to up
*Aug 13 14:33:40.884: %LINK-3-UPDOWN: Interface Serial1/0:15, changed state to up
*Aug 13 14:33:41.684: %CSM-5-PRI: add PRI at 0/0/1:15 (index 0)
*Aug 13 14:33:41.688: %CSM-5-PRI: add PRI at 0/0/0:15 (index 1)
*Aug 13 14:33:51.648: %CSM-5-PRI: add PRI at 1/0:15 (index 2)
*Aug 13 14:34:14.956: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 0 state Standby -> Active
*Aug 13 14:34:15.164: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 2 state Standby -> Active
*Aug 13 14:34:15.484: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 3 state Standby -> Active
*Aug 13 14:34:21.600: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.85.212 on GigabitEthernet0/1.86 from LOADING to FULL, Loading Done
*Aug 13 14:34:27.728: %HSRP-5-STATECHANGE: GigabitEthernet0/0.400 Grp 4 state Standby -> Active
*Aug 13 14:20:02.780: %SYS-5-PRIV_AUTH_FAIL: Authentication to privilege level 15 failed by xxxx on vty0 (xxxx)
*Aug 13 14:21:50.405: %SYS-5-CONFIG_I: Configured from console by av-vilenko on vty0 (xxxx)

i made some changes, but nothing that would or could cause this. And besides according to my collegues its not a recent problem (before i joined the company), it goes back at least a year or more...but ofc. since router is working fine untill you try to show the config noone bothered to resolve the issue they just kept their hands off it -.-

ASE instance not available *** ERROR:ASE instance possibly left running when system went down(system crash?). Notify Database Administrator

Hi Gurus,
I made some changes in rz10 for client copy like:
icm/host_name_full [email protected]
login/accept_sso2_ticket 1
login/create_sso2_ticket 2
icm/server_port_1
PROT=HTTPS,PORT=443$$,PROCTIMEOUT=600,TIMEOUT=600
icm/server_port_0
PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600
login/no_automatic_user_sapstar 0
After to make changes effective, i stopsap & startsap.
But unfortunately db is not coming up. I checked startdb.log it showing
error as " ASE instance not available
*** ERROR:ASE instance possibly left running when system
went down(system crash?).
Notify Database Administrator."
Please help us to resolve this issue, i have also added startdb.log for
your reference.
Regards,
Piyush

Hi Piyush,
Did you solved this issue.
We are facing the same issue and only this thread is there in SCN for this issue.
If you solved this issue,Kindly share the solution.
Thanks and Regards,
Mathan A

SMTP Service crashes when i enable reserve lookup?

I have got NMS 4.15 running on linux. When i enable reverse lookup my SMTP services starts crashing. Can anybody tell me what is the solution to this?

I'm not an NMS guru by any means.
First, 4.15 is older, get 4.17, at least the SMTP daemon.
Second, get off of NMS ASAP. :) Seriously, NMS has problems and the sooner you migrate to iMS the happier you will be. I realize that iMS does not run on Linux right now. I suspect that iMS 6 will be supported on Linux.
Why do you want to turn on reverse lookup? Sure you'll get some nice name in your headers instead of only IP address but your performance will also suffer.
-Chad-

My computer is crashed after 3 hours, when am running an Executable file from LabView 6.0.2

My VI is using DAQ6025e and GPIB cards, it is countiniusly writing data to files and talking with 2 GPIB instruments and one Serial instrument. Sudenly after 3 hours of perfect working it is crash my computer.
Does any body know why ??? Help? S.O.S?

Some questions to help us troubleshoot:
1)How crashed is your computer when it crashes?
Blue Screen Of Death crashed? If you don't know about BSOD then that
is when your computer presents a blue screen (white in XP) and tells
you that the system is halted, gives you a register dump and the
memory address where it stopped (all of which is useless unless you
are an assembly language wizard) and then you have to reboot the
machine.
Application error that kills LabVIEW.exe? Usually a pop-up MSGBOX
style dialog box will appear with a such and such error occurred in
LabVIEW.exe or another application and an OK button.
VI Slows to a crawl w/hourglass in the app window? Program doesn't
stop executing, it just stops responding to user inputs.
LabVIEW error cluster error that causes the VI to quit?
2) What O/S are you running? Win 3.1, Win 95, Win 98, Win NT 3.1, Win
NT 3.5, Win NT 4.0, Win2000, WinME, WinXPHome, Win XPPro?, Linux?, Mac
O/S?
In the Microsoft family, WinNT and Win2000 are by far the most stable
and reliable of the various versions of Windows with Win95 and Win98
having a lot of problems running for long periods of time. Make sure
that you get WinNT 4.0 updated to service pack 6 if you are still
using 4.0 but haven't updated the service pack level yet. There were
quite a number of problems with it when it first came out that have
since been cured.
3) Have you run the LabVIEW VI profiler yet? This will point out
memory leaks that are due to dynamically built arrays using shift
registers etc. or appending to strings, or improper IMAQ management,
etc.
4) Have you brought up the task manager and looked at the memory
allocated for LabVIEW.exe and for the whole system as well? Is it
growing? Sometimes there can be memory leaks that don't show in the
profiler that will show in the task manager when you look. These can
be due to bugs in LabVIEW itself or some driver for some hardware you
are using, etc.
If you are not running NT or a later derivative, then you won't have
task manager available but you can get diagnostic tools that are very
similar to task manager from off the web.
5) How much memory do you have in your PC? How fast is your PC? What
does the CPU % usage look like under task manager when you first start
your app? If it is running >40% CPU usage for any significant amount
of time at the start then perhaps your PC is overloaded with work and
you need a faster PC or your code needs redesigning. I like data
acquisition systems to operate <25% generally speaking. This number
seems to improve the reliability of the code that is running on them.
6) How much H/D space is available? You say you are writing data to
files. Your h/d space isn't running out is it?
7) Is it possible to run one instrument at a time for several hours to
see if it is a particular instrument that is causing the crash? Make
sure that your GPIB cards are properly configured so that they don't
share resources with any other devices(IRQ, DMA, memory addresses,
etc.) It may be possible that they behave fine most of the time even
with shared resources but if they ever try to send a command
simultaneously and they share resources, they could "collide" and
crash your PC. You can check all this out in the control panel and/or
MAX.
8) Is it possible that your serial port is getting hung up after
running a long period of time? Serial port UARTS are notoriously
finicky especially over longer line lengths and higher data rates. It
could be that your serial instrument is locking up your app or your PC
serial port is locking up your app and causing the crash. Can you put
a serial port analyzer in between your serial instrument and your PC
to see what's going on when it crashes?
9) Are you trying to read or write to the serial port in more than one
thread or while loop or dynamically launched vi? If you are you MUST
protect the serial port access with a semaphore or a VISA resource
lock. You CANNOT use a boolean global to protect access. Regular
globals aren't atomic and you can have race conditions that result in
unintended serial port collisions between differen threads. I have
seen this lock up multi-threaded serial programs before to the point
of requiring rebooting.
This problem can be especially frustrating if you haven't done
multi-threaded before. The port won't necessarily lock up right away
or at the same time every time. You MUST make sure that serial port
access is limited to ONLY ONE execution thread at a time.
10) Is there another application or service running in the background
with your application that may be trying to access the serial port or
GPIB cards when you aren't expecting it? This could cause a collision
that could crash your system as well.
Douglas De Clue
LabVIEW developer
[email protected]
Yan wrote in message news:<[email protected]>...
> My VI is using DAQ6025e and GPIB cards, it is countiniusly writing
> data to files and talking with 2 GPIB instruments and one Serial
> instrument. Sudenly after 3 hours of perfect working it is crash my
> computer.
> Does any body know why ??? Help? S.O.S?

Hi Team, Showing Yellow icons after every 15 to 20 Min and internet stop working.when we enable- disbale the network connection then will internet start working fine.Some time network connection is disable but when we renable that connection it will st

Hi Team,
Showing Yellow icons after every 15 to 20 Min and internet stop working.when we enable- disbale the network connection then will internet start working fine.Some time network connection is disable but when we renable that connection it will stuck on enabling
and will not renable till i am not restart that machine. I have 350 Machine in network but facing this issue in 25 machines. Kindly help me on this issue .
Regards
Sahil bhateja

Hi，
So switch a LAN card fix this issue...seems a compatibility issue or maybe some packs or programs you installed recently cause this issue.
Have you manually check the network adapter driver from the PC's manufacture website? sometimes, it will be a time delay before Microsoft push out the driver update.
Check if issue exists in safemode with network, this mode will launch Windows with limited sets of files and drivers.
if you have a restore point, restore the pc to a previous point at which the pc is functioning fine.
Yolanda Zhu
TechNet Community Support

EMET 5.2 Crashes Outlook 2013 when EAF enabled

Question moved to https://social.technet.microsoft.com/Forums/en-US/78ed8791-9a77-40f5-abba-0fd35883ea36/emet-52-crashes-outlook-2013-when-eaf-enabled?forum=emet
Hi
I'm testing EMET 5.2 for deployment into our environment. However I've come across an issue which causes Outlook 2013 to crash when EAF is enabled.
The following is from the event log:
Faulting application name: OUTLOOK.EXE, version: 15.0.4711.1000, time stamp: 0x55091de4
Faulting module name: ntdll.dll, version: 6.3.9600.17736, time stamp: 0x550f4336
Exception code: 0xc0000005
Fault offset: 0x000000000005473b
Faulting process id: 0x1774
Faulting application start time: 0x01d078b41581d9d3
Faulting application path: C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 53710d64-e4a7-11e4-8277-60571871a781
Faulting package full name:
Faulting package-relative application ID:
Is there any way to have EAF enabled, or all good to leave it off the list?
Andrew

Hi,
Because of your problem is more relate with EMET, it would be better to post this problem at specific forum:
EMET Support:
https://social.technet.microsoft.com/Forums/en-US/home?forum=emet&filter=alltypes&sort=lastpostdesc
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Feature Request: Continue to show Info when using Crop tool

Way, way back, I don't remember how many versions in the past, Info would continue to show numbers when using the Crop tool. I was hoping this might return in CS6, but it does not seem to be the case. I found this feature very useful when cropping product shots on a white background, which have a shadow and/or reflection at the base of the product. I don't want to crop into the shadow/reflection, but as they fade to white they get very light, of course, and difficult to see. I know I can make guides, etc., but I'd still love to have that feature return.
Thanks in advance,
Dan Clark
www.weinberg-clark.com

Yes, the Info panel. After making a selection (or whatever you want to call it) with the Crop tool, there are no longer any RGB or CMYK values (depends on what your preferences are set to, of course) in the Info panel. PS used to display values when using the Crop tool, but hasn't for quite a few versions.
Dan Clark
www.weinberg-clark.com

TableView Context Menu Item shows up when run on Java 8 until update 5 but not on later ones

The code below runs as its name says on Java 8 update 5 but not on later ones:
public class TableViewShowingOnlyAnAppendContextMenuItemIfRowIsEmptyElseDeleteIsIncluded extends Application {
    private final TableView<Name> table = new TableView<>();
    private final ObservableList<Name> data = FXCollections.observableArrayList(new Name("Jacob"),
            new Name("Isabella"), new Name("Ethan"), new Name("Emma"), new Name("Michael"));
    public static void main(String[] args) {
        launch(args);
    @Override
    public void start(Stage stage) {
        TableColumn<Name, String> column = new TableColumn<>("Name");
        column.setCellValueFactory(new PropertyValueFactory<>("name"));
        table.getColumns().add(column);
        table.setItems(data);
        ContextMenu contextMenu = new ContextMenu();
        contextMenu.getItems().add(new MenuItem("append"));
        table.setContextMenu(contextMenu);
        table.setRowFactory(tableView -> {
            TableRow<Name> row = new TableRow<>();
            row.contextMenuProperty().bind(
                    Bindings.when(Bindings.isNotNull(row.itemProperty()))
                            .then(showOnlyAppendContextMenuItemIfRowIsEmptyElseIncludeDelete())
                            .otherwise((ContextMenu) null));
            return row;
        Scene scene = new Scene(table);
        stage.setScene(scene);
        stage.show();
    private ContextMenu showOnlyAppendContextMenuItemIfRowIsEmptyElseIncludeDelete() {
        ContextMenu rowMenu = new ContextMenu();
        ContextMenu tableMenu = table.getContextMenu();
        if (tableMenu != null)
            rowMenu.getItems().addAll(tableMenu.getItems());
        rowMenu.getItems().add(new MenuItem("delete"));
        return rowMenu;
    public static class Name {
        private final SimpleStringProperty name;
        private Name(String name) {
            this.name = new SimpleStringProperty(name);
        public String getName() {
            return name.get();
        public void setName(String name) {
            this.name.set(name);
Can help me find the error in the code? Or if there is none, is this a regression that should be submitted? As of now, all the PCs in use have 8u5.
Thanks in advance.

Correctly answered by James_D:
http://stackoverflow.com/questions/28195552/javafx-tableview-context-menu-item-shows-up-when-run-on-java-8-until-update-5-bu
pasted below:
The fix is to create new menu items that are copies of the ones in the table's context menu:
private ContextMenu showOnlyAppendContextMenuItemIfRowIsEmptyElseIncludeDelete() {
ContextMenu rowMenu = new ContextMenu();
ContextMenu tableMenu = table.getContextMenu();
if (tableMenu != null) {
for (MenuItem item : tableMenu.getItems()) {
MenuItem rowItem = new MenuItem(item.getText());
rowItem.setGraphic(item.getGraphic());
rowItem.setOnAction(item.getOnAction());
rowMenu.getItems().add(rowItem);
rowMenu.getItems().add(new MenuItem("delete"));
return rowMenu;

Nokia 808 crashes periodically when 3G enabled (Ge...

Hi,
I have a Nokia 808 PureView Type RM-807, Software version 112.020.0309. I can provide more details if needed.
I bought this device in Ukraine because that's where I work. There is no WCDMA 3G in Ukraine. EDGE peformance in Ukraine was fine. Currently I am travelling my home country, Germany, and have got local (German) SIM cards from O2 and from Vodaphone with a 3G data plan and was expecting being to able my phone with 3G in Germany, but alas, I am not.
The issue is that while 3G works at first sight, with 3G enabled, my phone crashes on average once or twice a day. By "crashes" I mean that the screen either freezes or turns black and the only way to wake up the phone is to remove the battery.
The problem is exacerberated by bad operator connectivity. The first two weeks I stayed at a holiday resort by the sea where 3G quality was limited. There, my phone kept crashing every 30 minutes or so. I then disabled 3G and used EDGE and thought oh well maybe both O2 and Vodaphone just have a faulty base transmitter station here or something. However, I also see the crashes now in big cities where I have 5 bars quality and even while I stay stationary at one office with perfect 3G coverage. The crashes are less frequent here, I can work a couple of hours but all of a sudden, wosh, the screen goes black. Disabling 3G and using GRPS/EDGE solves the problem. I have not seen a single crash with 3G disabled, but GPRS enabled for all my stay in Germany which is now approaching 4 weeks. Everything is a bit more slow but works stably.
Now if I re-iterate the arguments from the Wi-Fi connectivity thread: Of course I am willing to accept that the 808 has got a perfect implementation of the standards and that the base transmitter stations of both O2 and Vodaphone are misbehaving. However I EXPECT MY PHONE TO WORK UNDER REAL LIFE CONDITIONS. No matter how the BTS misbehaves, under no circumstances should my phone crash becaus of that!!! If 3G is flawy, it should fall back to EDGE and that's it! And I also can't help but notice that I also carry my old Nokia 5800 with me which is also a Ukrainian model but it has no issue at all with German 3G operators.
Speaking of "Ukraine" devices, I am still at FW 309 because no newer updates were made available to me so far. Maybe the 808 sold in Germany comes with a newer firmware with operator-specific fixes? Is there a way to get the newer firmware versions (I read about 310 and 311 on symbiantweet) for my phone? And why does Nokia not deploy all operator-specific fixes to all devices? After all you can never know where the customer will be travelling ...
I will be staying in Germany until end of August. I am able to reproduce the crashes at the office am currently working in, so we have some reproducable scenario. However they don't happen that often here, it is like once every other day, so not optimum testing conditions unfortunately. I can profide full cell/operator information as provided by PhoNetInfo or any other diagnosis tool if you let me know which one.
I have quite some data conusmers installed on my phone, there is the Facebook widget, the e-mail widget with a fastmail.fm IMAP account, the weather widget, and I frequently browse the web, use apps like FlickrUp to upload photos and so on. Initially, I also had installed WhatsApp, but that was the first app that I deinstalled when the phone started crashing, however, deinstalling did it not help at all.
Any thoughts welcome, I am willing to help with diagnosing the issue.
Best regards,
Tobias
www.tf-translate.net
www.deutscheschule.kiev.ua
Solved!
Go to Solution.

Dear Kosh,
I resetted my device a couple of weeks ago because of the Wi-Fi trouble reported in an independent thread, just to be sure that my phone was 100% "virgin". I did not restore any kind of backup after that but re-did all necessary settings, installs etc. manually and copied some of the old photos to the mass memory, that's it.
On a second thought, a source of trouble that should be eliminated could be WhatsApp. I read a while ago that users were having crashes with WhatsApp and not having crashes when de-instlaling WhatsApp. So very extremely hypothetically, WhatsApp could have done something to my phone that makes it crash even after WhatsApp and all its related helper apps have been uninstalled. So I could do another reset cycle and not install WhatsApp at all. I don't need WhatsApp anyway.
Your advice of only making the most necessary settings is difficult to follow, because the crashes are more or less related to the amount of internet activity (either data volume or number of connections, I am not sure). No activity - no crash, the crashes always occur while I am doing something on the phone (that something could be anything - calling, browsing photos, uploading stuff to flickr, reading news with the pre-installed reuters app, trying to book a train ticket with DB navigator, ...). So I need to configure at least the built-in Nokia applications (mail, social network) and install some 3d party apps in order to be able to work on the phone enough to trigger the issue. What I could to is to leave out the "always on" apps like WhatsApp and TotalRecall. As I said, I will try to find a time window to do it.
Also, the crashes are not that often in the place where I am currently. Today I had 3G enabled the whole day and had a lot of VoIP and other activity, but the phone kept stable. I could of course book another holiday at that seaside with its flaky 3G connection for further debugging purposes, but that would be more expensive than getting a competitor's device plus a standalone camera ;-).
My product code is 059M7H1. Is there any firmware more recent than the 112.020.0309.C00.01 that i currently have?
Best regards,
Tobias
www.tf-translate.net
www.deutscheschule.kiev.ua

SPS224G4 crash on show run when features enables over SNMP

Similar Messages

Maybe you are looking for