Configuration error #1434

tsalzer · Tue Jul 11, 2006 5:56 pm

Just installed StarPort Pro 3.0.2, and it is throwing up a configuration error #1434. What does this mean?

StarPort is installed on a Windows Storage Server 2003 box, connected by Ethernet directly to a CoRAID SR420 with four 500 Gb drives in RAID 5. I initialized the array through Windows, converted it to a dynamic disk and formatted. I can see it, but I can't access it.

Tom

Val (staff) · Tue Jul 11, 2006 8:13 pm

tsalzer wrote:Just installed StarPort Pro 3.0.2, and it is throwing up a configuration error #1434. What does this mean?

StarPort is installed on a Windows Storage Server 2003 box, connected by Ethernet directly to a CoRAID SR420 with four 500 Gb drives in RAID 5. I initialized the array through Windows, converted it to a dynamic disk and formatted. I can see it, but I can't access it.

Tom

Hi Tom,

The "configuration error #1434" message means there is another instance of StarPort in the network that uses the same license ID.
A Personal or a Professional license is to be used for a single host only.

Please read StarPort 3.0 Licensing Information for more details.

tsalzer · Tue Jul 11, 2006 8:18 pm

Thank you Valeriy.

The CoRAID device is connected directly to the Windows Storage Server 2003 platform by CAT 6 cable. I installed the StarPort driver once, on the Win Server.

To my knowledge there is no other instance of StarPort on the network.

Are there other possible causes of this error? Note that I'm using version 3.0.2 because that's what I got in the mail a few days ago.

Tom

Val (staff) · Tue Jul 11, 2006 9:02 pm

tsalzer wrote:Thank you Valeriy.

The CoRAID device is connected directly to the Windows Storage Server 2003 platform by CAT 6 cable. I installed the StarPort driver once, on the Win Server.

To my knowledge there is no other instance of StarPort on the network.

Are there other possible causes of this error? Note that I'm using version 3.0.2 because that's what I got in the mail a few days ago.

Tom

Tom,

Please check it whether the only StarPort.exe instance is running inside the server.
This could be the case if you use 2+ RDP sessions to the server.

tsalzer · Tue Jul 11, 2006 9:27 pm

Thank you. I did have two RDP sessions going. I've terminated one and things look fine now.

Is there a FAQ or directions on upgrading? I have version 3.0.2, but the current release appears to be 3.0.4.

Thanks again,

Tom

Val (staff) · Tue Jul 11, 2006 9:50 pm

tsalzer wrote:Thank you. I did have two RDP sessions going. I've terminated one and things look fine now.

Is there a FAQ or directions on upgrading? I have version 3.0.2, but the current release appears to be 3.0.4.

Thanks again,

Tom

Glad to hear it! :)

To upgrade to v3.0.4 just install it over your v3.0.2 and reboot the machine.
It's recommended to dismount all devices from StarPort before upgrading.

Bill.French · Mon Aug 20, 2007 3:06 pm

Thank you. I did have two RDP sessions going. I've terminated one and things look fine now.

Has this issue related to RDP been fixed in 3.5? Thanks, --Bill

Tue Aug 21, 2007 10:48 am

Hi.
Yes, this issue has been fixed.