jace 201, 3.1.29 to 3.3

[amigo]

I had an older jace 201 (1 year old) which I worked on with workbench 3.1.29 with no problems.

I upgraded my workbech to 3.3, connected to this old jace and told it to update all out of date modules.

Now, no platform or station connection.

Am I hooped? My choices are?

[sysint]

Hmmm. You said "hooped".

[freddy-b]

I had an older jace 201 (1 year old) which I worked on with workbench 3.1.29 with no problems.

I upgraded my workbech to 3.3, connected to this old jace and told it to update all out of date modules.

Now, no platform or station connection.

Am I hooped? My choices are?

Hooped is a nice way to say it, but yes you are!

[The Dog]

Did you upgrade the Jace or are you talking about upgrading your laptop?
If you upgraded the JACE with no liscence upgrade, you are 'hooped' until you get an upgraded liscense.
If you are talking about your laptop, just open the rev level that is on the JACE and connect to it.

Oops, I just reread and you said no platform or station connection, so you must have upgraded the JACE. I believe you need to pay for liscense upgrade.

[freddy-b]

Did you upgrade the Jace or are you talking about upgrading your laptop?
If you upgraded the JACE with no liscence upgrade, you are 'hooped' until you get an upgraded liscense.
If you are talking about your laptop, just open the rev level that is on the JACE and connect to it.

Oops, I just reread and you said no platform or station connection, so you must have upgraded the JACE. I believe you need to pay for liscense upgrade.

I believe its even worse than that. I dont think you can do anything with it in the field. I may be wrong, but I think its hosed.

[amigo]

Yeah, I think it is hosed.

Just so it does not happen again, where do I check on jace to see up to what version I can go up to?

Also, why would there not be a check by Jace before it does this? I mean it just makes sense to throw an exception and say no go instead of hosing itself.

[NINAX]

Yeah, I think it is hosed.

Just so it does not happen again, where do I check on jace to see up to what version I can go up to?

Also, why would there not be a check by Jace before it does this? I mean it just makes sense to throw an exception and say no go instead of hosing itself.

I would think you should still be able to get a platform connection if it is 'just' a license problem. The license will just prevent you from running a station. I'd do the port dump and see what is returned.

You could/may be able to downgrade with the clean dist to 3.1. I believe 3.3 contains them. Boot up your help in workbench and search clean. It should be the first thing that returns.

Additionally, you might want to review AX Upgrades and Downgrades (http://www.niagara-central.com/ord?portal:/blog/BlogEntry/154)

[NINAX]

Yeah, I think it is hosed.

Just so it does not happen again, where do I check on jace to see up to what version I can go up to?

Also, why would there not be a check by Jace before it does this? I mean it just makes sense to throw an exception and say no go instead of hosing itself.

If you upgrade, as ChrisW advocates, one of the selections is install license.

I guess they figure that if you're upgrading, you know that the new license must be installed as part of the process.

[freddy-b]

I would think you should still be able to get a platform connection if it is 'just' a license problem. The license will just prevent you from running a station. I'd do the port dump and see what is returned.

You could/may be able to downgrade with the clean dist to 3.1. I believe 3.3 contains them. Boot up your help in workbench and search clean. It should be the first thing that returns.

Additionally, you might want to review AX Upgrades and Downgrades (http://www.niagara-central.com/ord?portal:/blog/BlogEntry/154)

Ya, but its too late now..right?

[amigo]

If you upgrade, as ChrisW advocates, one of the selections is install license.

I guess they figure that if you're upgrading, you know that the new license must be installed as part of the process.

I understand what you are saying.

But I still say Jace should be smart enough not to hose itself.

I have no platform connection, so it is stuck somewhere.

I will do the port dump, and make the support call.

Thanks for the replies.

[freddy-b]

I understand what you are saying.

But I still say Jace should be smart enough not to hose itself.

I have no platform connection, so it is stuck somewhere.

I will do the port dump, and make the support call.

Thanks for the replies.

Oh I agree. I made the the mistake of changing the hostname in platform admin , on a PC running webstation. Bad, bad news it screws ya real good.

[NINAX]

I understand what you are saying.

But I still say Jace should be smart enough not to hose itself.

I have no platform connection, so it is stuck somewhere.

I will do the port dump, and make the support call.

Thanks for the replies.

What you did, the process (loosely), is what I would do when upgrading. But you need to make sure you have the license before upgrading.

I suppose they could have three or four pop-ups asking you "are sure you want to upgrade?' and 'please verify you have a license for this station before continuing' and then 'are you really sure?'

But, even with all of that, it still just boils down to the same thing that you should know to check before upgrading.

[Chris_Worthington]

If you upgrade, as ChrisW advocates, one of the selections is install license.

I guess they figure that if you're upgrading, you know that the new license must be installed as part of the process.


Once you get into the platform administrator, on one the very top lines to the left will indicate the version number of the Jace you are logged into.

You MUST have an updated license prior to upgrading !!! you can view and or install/upgrade your license via viewing the license manager.

You can also do this during a wizard commish, select to install a license from a file "OR" online, your choice, but it better be there :)

The Jace is only as smart as its operator and it sounds like you jumped the gun :eek:

The Trids might be able to help you out, get together the information you have and give them a buzz ;)

[NINAX]

Ya, but its too late now..right?

It depends on what went wrong. But if it was simply upgraded, it should downgrade just fine.

BUT FOLLOW THE DOWNGRADE/CLEAN DIST INSTALL DIRECTIONS!
DO NOT DEVIATE FROM THE INSTRUCTIONS!
Or you will be boxing it up and sending it in for repair.

[Chris_Worthington]

NINAX,

I like your new avatar :D

[freddy-b]

It depends on what went wrong. But if it was simply upgraded, it should downgrade just fine.

BUT FOLLOW THE DOWNGRADE/CLEAN DIST INSTALL DIRECTIONS!
DO NOT DEVIATE FROM THE INSTRUCTIONS!
Or you will be boxing it up and sending it in for repair.

How do you get back into platform now?

[NINAX]

How do you get back into platform now?

That, I can't answer.
Again, the license would just prevent a station from running. You should still be able to connect and see in the App Director, and it would say that the JACE is not license to run a station.

That's why I'd do a dump and see what it spits out.

[amigo]

The Jace is only as smart as its operator and it sounds like you jumped the gun :eek:

The Trids might be able to help you out, get together the information you have and give them a buzz ;)

No question that I jumped the gun, :D

but still say the Jace should have checked my breath, can't let a drunk do the upgrades, :p

[Chris_Worthington]

There are ways to recover, BUT at this point it may be best contact the Trids and have them WALK you through this, Should you be able to recover out of this mess, you have lived and learned ;)

[tk2k]

I would go into that bad boy through hyperterminal/Serial Shell mode.

It may give you some information in the boot up. Boot Flash Errors and so on.

[amigo]

I would go into that bad boy through hyperterminal/Serial Shell mode.

It may give you some information in the boot up. Boot Flash Errors and so on.

This is through serial shell at startup:

>>>>>>>>>>>>
----------------------TCP/IP Network Status------------------------------
en0: flags=8c43<UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST> mtu 1500
address: 00:01:f0:80:47:58
inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255
en1: flags=8c43<UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST> mtu 1500
address: 00:01:f0:80:47:59
inet 192.168.0.6 netmask 0xffffff00 broadcast 192.168.0.255
-------------------------------------------------------------------------

JACE-2 Base Board detected
LON interface detected
MESSAGE [15:24:21 20-Oct-2008] [tid=1] niagarad: starting, baja_home=/niagara
MESSAGE [15:24:21 20-Oct-2008] [tid=1] webserver: web server started [tid = 4]
MESSAGE [15:24:21 20-Oct-2008] [tid=1] station registry: starting
MESSAGE [15:24:21 20-Oct-2008] [tid=7] app: starting watchdog thread
MESSAGE [15:24:21 20-Oct-2008] [tid=7] niagarad: Communications_Inc start
ing
login: MESSAGE [15:24:35 20-Oct-2008] [tid=7] niagarad: Communications_In
c exited with status 0
sysmon: j9 is no longer running
>>>>>>>>>>>>>>>

Talked to non-tridium contact, they say have to send it back.

Waiting to see if I can talk to Trids directly before boxing it.

[beenaxed]

In the Tridium world, upgrade is a French word for you're ________ed.
Been there, done that -- even with a new license and had problems. Stay with the version that you started the job with.

[NINAX]

In the Tridium world, upgrade is a French word for you're ________ed.
Been there, done that -- even with a new license and had problems. Stay with the version that you started the job with.

I'd say some more training would handle your issues.

I've had ZERO problems upgrading with the new license.

[Chris_Worthington]

I'd say some more training would handle your issues.

I've had ZERO problems upgrading with the new license.

I'll second the zero issues, but I have heard of some having some. It seems it always has something to do with NOT following the instructions :eek:

[jogas]

Did you try connecting to the Platform with 3.1? May be worth a try? At least the License version will match.
I Keep AX 3.0.99, 3.1.29, 3.1.30, and 3.3.22 running on my laptop for different jobs we've installed. I just run the platform daemon for whatever version I need to run before booting up that corresponding version.