Sage 100

I have a customer who recently ( within the prior month ) had V-Technologies install an upgrade to their on-prem. Is there a separate place that says they won't support on-prem?  I'm pretty sure V-Tech installed 24.0.2 and also the Web Client on-premise.

I do recall rumblings that V-Technologies was stopping support for on-prem StarShip but thought that had been delayed?

I have heard nothing about ending completely on-premise installs.  I have two clients that are going to struggle with the Web-Client (on premise has to use it); or if they decide to go StarShip Cloud (which uses it).  They will struggle with the changes. 

I have a customer who recently ( within the prior month ) had V-Technologies install an upgrade to their on-prem. Is there a separate place that says they won't support on-prem?  I'm pretty sure V-Tech installed 24.0.2 and also the Web Client on-premise.

I do recall rumblings that V-Technologies was stopping support for on-prem StarShip but thought that had been delayed?

Here's a cross-reference to an earlier (12/8/2023) 90 Minds thread about Starship Cloud.

I also had ChatGPT summarize it to add background to this topic

I have heard nothing about ending completely on-premise installs.  I have two clients that are going to struggle with the Web-Client (on premise has to use it); or if they decide to go StarShip Cloud (which uses it).  They will struggle with the changes. 

I have a customer who recently ( within the prior month ) had V-Technologies install an upgrade to their on-prem. Is there a separate place that says they won't support on-prem?  I'm pretty sure V-Tech installed 24.0.2 and also the Web Client on-premise.

I do recall rumblings that V-Technologies was stopping support for on-prem StarShip but thought that had been delayed?

I think V-Technologies installed the hybrid for my customer. I'm unsure if they forced them to use the cloud UI, though. They mentioned that it would be needed soon, so they installed it. The V-Technologies tech also brought down my customer's Sage 100 by advising them that they could have people working in Sage during the V-Tech upgrade. Naturally, this upgrade crashed and took out a key data dictionary file. Luckily, we found a backup, but I am also wary of V-Technologies.

After V-Technologies performed their on-prem upgrade, the customer didn't have any issues-at least none I've heard about yet.

The V-Technologies tech was super rushed. It should be interesting to see how things roll as V-Technologies pushes further with their cloud product.

Here's a cross-reference to an earlier (12/8/2023) 90 Minds thread about Starship Cloud.

I also had ChatGPT summarize it to add background to this topic

I have heard nothing about ending completely on-premise installs.  I have two clients that are going to struggle with the Web-Client (on premise has to use it); or if they decide to go StarShip Cloud (which uses it).  They will struggle with the changes. 

I have a customer who recently ( within the prior month ) had V-Technologies install an upgrade to their on-prem. Is there a separate place that says they won't support on-prem?  I'm pretty sure V-Tech installed 24.0.2 and also the Web Client on-premise.

I do recall rumblings that V-Technologies was stopping support for on-prem StarShip but thought that had been delayed?

My last upgrade actually went really well.  No issues, tech was willing to answer any questions the client had (up to the time limit of the meeting, but she covered everything they asked).  

------------------------------
Beth Bowers
(269) 358-0989
------------------------------


Original Message:
Sent: 04-12-2024 11:47
From: Wayne Schulz
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

I think V-Technologies installed the hybrid for my customer. I'm unsure if they forced them to use the cloud UI, though. They mentioned that it would be needed soon, so they installed it. The V-Technologies tech also brought down my customer's Sage 100 by advising them that they could have people working in Sage during the V-Tech upgrade. Naturally, this upgrade crashed and took out a key data dictionary file. Luckily, we found a backup, but I am also wary of V-Technologies.

After V-Technologies performed their on-prem upgrade, the customer didn't have any issues-at least none I've heard about yet.

The V-Technologies tech was super rushed. It should be interesting to see how things roll as V-Technologies pushes further with their cloud product.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 04-12-2024 11:43
From: Wayne Schulz
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

Here's a cross-reference to an earlier (12/8/2023) 90 Minds thread about Starship Cloud.

I also had ChatGPT summarize it to add background to this topic

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 04-12-2024 11:31
From: Madeline Stefanou
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

I have heard nothing about ending completely on-premise installs.  I have two clients that are going to struggle with the Web-Client (on premise has to use it); or if they decide to go StarShip Cloud (which uses it).  They will struggle with the changes. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 04-12-2024 11:17
From: Wayne Schulz
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

I have a customer who recently ( within the prior month ) had V-Technologies install an upgrade to their on-prem. Is there a separate place that says they won't support on-prem?  I'm pretty sure V-Tech installed 24.0.2 and also the Web Client on-premise.

I do recall rumblings that V-Technologies was stopping support for on-prem StarShip but thought that had been delayed?

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

We had a meeting with V-Technologies today and I'm not a fan.

@Wayne Schulz we are scrambling to upgrade all our "on premise clients" to 24.0.3 before June 1st then again to v24.0.4 before August 1st to handle UPS/FedEx OAuth requirements. 

Honestly, the quotes they have been giving our clients for this upgrade is "ridiculous".  One of our clients was quoted "Cloud/Professional" pricing which will take them from paying On Premise annual fees of $4,700 for the 2024 renewal (2023 renewal was $3812) to paying annual fees of $10,608 for Cloud PLUS their $ 3600 on board fee.  And if they were to sign today for Cloud, they STILL have to go to those versions in their on premise version before June 1.  Their fee to have V-Technology do the upgrade was also a crazy fee of $ 3800 for the By June1 part and additional $ 2800 for the by Aug. part.  

We had a meeting with V-Technologies today and I'm not a fan.

@Wayne Schulz we are scrambling to upgrade all our "on premise clients" to 24.0.3 before June 1st then again to v24.0.4 before August 1st to handle UPS/FedEx OAuth requirements. 

Honestly, the quotes they have been giving our clients for this upgrade is "ridiculous".  One of our clients was quoted "Cloud/Professional" pricing which will take them from paying On Premise annual fees of $4,700 for the 2024 renewal (2023 renewal was $3812) to paying annual fees of $10,608 for Cloud PLUS their $ 3600 on board fee.  And if they were to sign today for Cloud, they STILL have to go to those versions in their on premise version before June 1.  Their fee to have V-Technology do the upgrade was also a crazy fee of $ 3800 for the By June1 part and additional $ 2800 for the by Aug. part.  

We had a meeting with V-Technologies today and I'm not a fan.

Does anyone else feel like V-Technologies underestimated the difficulty of migrating customers from on-premise software to Starship Cloud? It seems like they focused heavily on developing Starship Cloud, and now they're scrambling to get existing customers on board.

I think UPS announced this OAuth 2.0 requirement well before now. It seems like they mentioned it at least a year ago. It's unlikely that UPS would suddenly put everyone in a difficult position by making many shipping packages non-compliant in June 2024 without ample warning. ( Source: UPS Site )

V-Technologies might want to reconsider highlighting their past warnings about this transition. Sending notices in March or April 2024 for a June deadline, along with costly service and cloud subscription quotes, puts significant pressure on their customers. 

This is a terrible situation from my vantage point. 

We are scrambling, too, and I have some additional information, as I'm learning along with you.  I don't have access to the Google docs project plan link, so not sure if this information is in there. If I can get access or someone can send it to me, I'd appreciate that.

From what I understand (and I asked Abel at VTech), the on prem client will still work, even if the customer is using the Starship Link.  Then, when they can, the shippers can explore, or we can train them on, the web client. 

After you load the new system (both the on prem and web client), you need to let StarShip know so they can turn on the OAuth for UPS on their end and then we need to do something with the registry on the client's server. 

KBA regarding Regkey for UPS OAuth and our help guide to setup in Web UI. 

https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions" rel="noopener">https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions

https://ask.vtechnologies.com/kb/ups-oauth-account-setup/" rel="noopener">https://ask.vtechnologies.com/kb/ups-oauth-account-setup/

I put my NFR copy upgrade yesterday.  I haven't yet followed the instructions above for my installation to move to OAuth and UPS is failing.  Not surprising.  Fed Ex is OK.  

Version 24.0.3 came out late last week. 

Roberta

CBIZ CompuData

Does anyone else feel like V-Technologies underestimated the difficulty of migrating customers from on-premise software to Starship Cloud? It seems like they focused heavily on developing Starship Cloud, and now they're scrambling to get existing customers on board.

I think UPS announced this OAuth 2.0 requirement well before now. It seems like they mentioned it at least a year ago. It's unlikely that UPS would suddenly put everyone in a difficult position by making many shipping packages non-compliant in June 2024 without ample warning. ( Source: UPS Site )

V-Technologies might want to reconsider highlighting their past warnings about this transition. Sending notices in March or April 2024 for a June deadline, along with costly service and cloud subscription quotes, puts significant pressure on their customers. 

This is a terrible situation from my vantage point. 

Fyi re: 24.0.3, this just came across my desk (orig from Simon at VTech):

We ran into an issue with a group of Sage 100 Link users who upgraded to v.24.0.3 and our Dev team has been working on a fix the last few days so we are asking customers to install v.24.0.2 for now since that works just fine and the users can authenticate their UPS accounts still on that version. 

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------


Original Message:
Sent: 04-30-2024 10:29
From: Roberta Chase
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

We are scrambling, too, and I have some additional information, as I'm learning along with you.  I don't have access to the Google docs project plan link, so not sure if this information is in there. If I can get access or someone can send it to me, I'd appreciate that.

From what I understand (and I asked Abel at VTech), the on prem client will still work, even if the customer is using the Starship Link.  Then, when they can, the shippers can explore, or we can train them on, the web client. 

After you load the new system (both the on prem and web client), you need to let StarShip know so they can turn on the OAuth for UPS on their end and then we need to do something with the registry on the client's server. 

KBA regarding Regkey for UPS OAuth and our help guide to setup in Web UI. 

https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions" rel="noopener">https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions

https://ask.vtechnologies.com/kb/ups-oauth-account-setup/" rel="noopener">https://ask.vtechnologies.com/kb/ups-oauth-account-setup/

I put my NFR copy upgrade yesterday.  I haven't yet followed the instructions above for my installation to move to OAuth and UPS is failing.  Not surprising.  Fed Ex is OK.  

Version 24.0.3 came out late last week. 

Roberta

CBIZ CompuData

Does anyone else feel like V-Technologies underestimated the difficulty of migrating customers from on-premise software to Starship Cloud? It seems like they focused heavily on developing Starship Cloud, and now they're scrambling to get existing customers on board.

I think UPS announced this OAuth 2.0 requirement well before now. It seems like they mentioned it at least a year ago. It's unlikely that UPS would suddenly put everyone in a difficult position by making many shipping packages non-compliant in June 2024 without ample warning. ( Source: UPS Site )

V-Technologies might want to reconsider highlighting their past warnings about this transition. Sending notices in March or April 2024 for a June deadline, along with costly service and cloud subscription quotes, puts significant pressure on their customers. 

This is a terrible situation from my vantage point. 

I've been reaching out to Sage 100 customers I know who use Starship, and so far, at least two of them say they have not received any notice from V-Technologies. I'm not sure whether this will snowball or be a faux issue, much like Sage OAUTH/Paperless.

I'm at least letting the customer know of the potential issue so that I'm not blamed.

Fyi re: 24.0.3, this just came across my desk (orig from Simon at VTech):

We ran into an issue with a group of Sage 100 Link users who upgraded to v.24.0.3 and our Dev team has been working on a fix the last few days so we are asking customers to install v.24.0.2 for now since that works just fine and the users can authenticate their UPS accounts still on that version. 

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 04-30-2024 10:29
From: Roberta Chase
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

We are scrambling, too, and I have some additional information, as I'm learning along with you.  I don't have access to the Google docs project plan link, so not sure if this information is in there. If I can get access or someone can send it to me, I'd appreciate that.

From what I understand (and I asked Abel at VTech), the on prem client will still work, even if the customer is using the Starship Link.  Then, when they can, the shippers can explore, or we can train them on, the web client. 

After you load the new system (both the on prem and web client), you need to let StarShip know so they can turn on the OAuth for UPS on their end and then we need to do something with the registry on the client's server. 

KBA regarding Regkey for UPS OAuth and our help guide to setup in Web UI. 

https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions" rel="noopener">https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions

https://ask.vtechnologies.com/kb/ups-oauth-account-setup/" rel="noopener">https://ask.vtechnologies.com/kb/ups-oauth-account-setup/

I put my NFR copy upgrade yesterday.  I haven't yet followed the instructions above for my installation to move to OAuth and UPS is failing.  Not surprising.  Fed Ex is OK.  

Version 24.0.3 came out late last week. 

Roberta

CBIZ CompuData

Does anyone else feel like V-Technologies underestimated the difficulty of migrating customers from on-premise software to Starship Cloud? It seems like they focused heavily on developing Starship Cloud, and now they're scrambling to get existing customers on board.

I think UPS announced this OAuth 2.0 requirement well before now. It seems like they mentioned it at least a year ago. It's unlikely that UPS would suddenly put everyone in a difficult position by making many shipping packages non-compliant in June 2024 without ample warning. ( Source: UPS Site )

V-Technologies might want to reconsider highlighting their past warnings about this transition. Sending notices in March or April 2024 for a June deadline, along with costly service and cloud subscription quotes, puts significant pressure on their customers. 

This is a terrible situation from my vantage point. 

I've been reaching out to Sage 100 customers I know who use Starship, and so far, at least two of them say they have not received any notice from V-Technologies. I'm not sure whether this will snowball or be a faux issue, much like Sage OAUTH/Paperless.

I'm at least letting the customer know of the potential issue so that I'm not blamed.

Fyi re: 24.0.3, this just came across my desk (orig from Simon at VTech):

We ran into an issue with a group of Sage 100 Link users who upgraded to v.24.0.3 and our Dev team has been working on a fix the last few days so we are asking customers to install v.24.0.2 for now since that works just fine and the users can authenticate their UPS accounts still on that version. 

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 04-30-2024 10:29
From: Roberta Chase
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

We are scrambling, too, and I have some additional information, as I'm learning along with you.  I don't have access to the Google docs project plan link, so not sure if this information is in there. If I can get access or someone can send it to me, I'd appreciate that.

From what I understand (and I asked Abel at VTech), the on prem client will still work, even if the customer is using the Starship Link.  Then, when they can, the shippers can explore, or we can train them on, the web client. 

After you load the new system (both the on prem and web client), you need to let StarShip know so they can turn on the OAuth for UPS on their end and then we need to do something with the registry on the client's server. 

KBA regarding Regkey for UPS OAuth and our help guide to setup in Web UI. 

https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions" rel="noopener">https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions

https://ask.vtechnologies.com/kb/ups-oauth-account-setup/" rel="noopener">https://ask.vtechnologies.com/kb/ups-oauth-account-setup/

I put my NFR copy upgrade yesterday.  I haven't yet followed the instructions above for my installation to move to OAuth and UPS is failing.  Not surprising.  Fed Ex is OK.  

Version 24.0.3 came out late last week. 

Roberta

CBIZ CompuData

Does anyone else feel like V-Technologies underestimated the difficulty of migrating customers from on-premise software to Starship Cloud? It seems like they focused heavily on developing Starship Cloud, and now they're scrambling to get existing customers on board.

I think UPS announced this OAuth 2.0 requirement well before now. It seems like they mentioned it at least a year ago. It's unlikely that UPS would suddenly put everyone in a difficult position by making many shipping packages non-compliant in June 2024 without ample warning. ( Source: UPS Site )

V-Technologies might want to reconsider highlighting their past warnings about this transition. Sending notices in March or April 2024 for a June deadline, along with costly service and cloud subscription quotes, puts significant pressure on their customers. 

This is a terrible situation from my vantage point. 

Fyi re: 24.0.3, this just came across my desk (orig from Simon at VTech):

We ran into an issue with a group of Sage 100 Link users who upgraded to v.24.0.3 and our Dev team has been working on a fix the last few days so we are asking customers to install v.24.0.2 for now since that works just fine and the users can authenticate their UPS accounts still on that version. 

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------


Original Message:
Sent: 04-30-2024 10:29
From: Roberta Chase
Subject: V-Technology - Must be at 24.0.2 prior to June 1 to use UPS API and by Aug. 2024 for FedEx API

We are scrambling, too, and I have some additional information, as I'm learning along with you.  I don't have access to the Google docs project plan link, so not sure if this information is in there. If I can get access or someone can send it to me, I'd appreciate that.

From what I understand (and I asked Abel at VTech), the on prem client will still work, even if the customer is using the Starship Link.  Then, when they can, the shippers can explore, or we can train them on, the web client. 

After you load the new system (both the on prem and web client), you need to let StarShip know so they can turn on the OAuth for UPS on their end and then we need to do something with the registry on the client's server. 

KBA regarding Regkey for UPS OAuth and our help guide to setup in Web UI. 

https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions" rel="noopener">https://aptean2.force.com/support/s/article/Switch-to-UPS-OAuth-2-0-instructions

https://ask.vtechnologies.com/kb/ups-oauth-account-setup/" rel="noopener">https://ask.vtechnologies.com/kb/ups-oauth-account-setup/

I put my NFR copy upgrade yesterday.  I haven't yet followed the instructions above for my installation to move to OAuth and UPS is failing.  Not surprising.  Fed Ex is OK.  

Version 24.0.3 came out late last week. 

Roberta

CBIZ CompuData

Does anyone else feel like V-Technologies underestimated the difficulty of migrating customers from on-premise software to Starship Cloud? It seems like they focused heavily on developing Starship Cloud, and now they're scrambling to get existing customers on board.

I think UPS announced this OAuth 2.0 requirement well before now. It seems like they mentioned it at least a year ago. It's unlikely that UPS would suddenly put everyone in a difficult position by making many shipping packages non-compliant in June 2024 without ample warning. ( Source: UPS Site )

V-Technologies might want to reconsider highlighting their past warnings about this transition. Sending notices in March or April 2024 for a June deadline, along with costly service and cloud subscription quotes, puts significant pressure on their customers. 

This is a terrible situation from my vantage point. 

@Roberta Chase and @Madeline Stefanou have you started doing any of these and is it safe now to start at StarShip 24.0.3 if the customer is using StarShip Link?

Last call for me on this one before I jump in with upgrades. Any feedback and/or bugs? Is 24.0.2 with StarShip Link still the only stable option for a customer remaining on-prem.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

Last call for me on this one before I jump in with upgrades. Any feedback and/or bugs? Is 24.0.2 with StarShip Link still the only stable option for a customer remaining on-prem.

Doug,

I had the same error. I had to change the name of the StarShip Connector showing within StarShip Web: 

I believe I either clicked on the StarShip Connector name or had to click the little pencil (edit) icon to change the connector name.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

Last call for me on this one before I jump in with upgrades. Any feedback and/or bugs? Is 24.0.2 with StarShip Link still the only stable option for a customer remaining on-prem.

Thanks Wayne!  That's it.  For documentation: 

1. On the top menu bar click Setup
2. Click the three horizontal bars in the upper left corner.
3. Setup Home
4. Setup Your Source Interfaces
5. Click the pencil to the right of the appropriate interface.  ie "Sage 100 2022 StarShip Link"
6. Select a Connector - click the triangle on the right to list the connectors.

Doug,

I had the same error. I had to change the name of the StarShip Connector showing within StarShip Web: 

I believe I either clicked on the StarShip Connector name or had to click the little pencil (edit) icon to change the connector name.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

Thanks Wayne!  That's it.  For documentation: 

1. On the top menu bar click Setup
2. Click the three horizontal bars in the upper left corner.
3. Setup Home
4. Setup Your Source Interfaces
5. Click the pencil to the right of the appropriate interface.  ie "Sage 100 2022 StarShip Link"
6. Select a Connector - click the triangle on the right to list the connectors.

Doug,

I had the same error. I had to change the name of the StarShip Connector showing within StarShip Web: 

I believe I either clicked on the StarShip Connector name or had to click the little pencil (edit) icon to change the connector name.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

Last call for me on this one before I jump in with upgrades. Any feedback and/or bugs? Is 24.0.2 with StarShip Link still the only stable option for a customer remaining on-prem.

Doug,

I had the same error. I had to change the name of the StarShip Connector showing within StarShip Web: 

I believe I either clicked on the StarShip Connector name or had to click the little pencil (edit) icon to change the connector name.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

Last call for me on this one before I jump in with upgrades. Any feedback and/or bugs? Is 24.0.2 with StarShip Link still the only stable option for a customer remaining on-prem.

@Wayne Schulz   I sent an email to Matt St John at StarShip.  He mentioned that for the UPS account, the Web UI version will show that the UPS account is active because it's picking up the activation when it was done through the Desktop client. HOWEVER, you will still need to re-activate the UPS account through the Web UI version.  Did you do this for your customers and if so how did you do it?  I know how to get to Setup>carrier Interfaces>UPS.  Then what?

Doug,

I had the same error. I had to change the name of the StarShip Connector showing within StarShip Web: 

I believe I either clicked on the StarShip Connector name or had to click the little pencil (edit) icon to change the connector name.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

Last call for me on this one before I jump in with upgrades. Any feedback and/or bugs? Is 24.0.2 with StarShip Link still the only stable option for a customer remaining on-prem.

@Doug Higgs I've been reaching out to just about everyone on here who claims to deal with StarShip and it's mostly crickets chirping. I'll send you an email.

@Wayne Schulz   I sent an email to Matt St John at StarShip.  He mentioned that for the UPS account, the Web UI version will show that the UPS account is active because it's picking up the activation when it was done through the Desktop client. HOWEVER, you will still need to re-activate the UPS account through the Web UI version.  Did you do this for your customers and if so how did you do it?  I know how to get to Setup>carrier Interfaces>UPS.  Then what?

Doug,

I had the same error. I had to change the name of the StarShip Connector showing within StarShip Web: 

I believe I either clicked on the StarShip Connector name or had to click the little pencil (edit) icon to change the connector name.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

@Doug Higgs I've been reaching out to just about everyone on here who claims to deal with StarShip and it's mostly crickets chirping. I'll send you an email.

@Wayne Schulz   I sent an email to Matt St John at StarShip.  He mentioned that for the UPS account, the Web UI version will show that the UPS account is active because it's picking up the activation when it was done through the Desktop client. HOWEVER, you will still need to re-activate the UPS account through the Web UI version.  Did you do this for your customers and if so how did you do it?  I know how to get to Setup>carrier Interfaces>UPS.  Then what?

Doug,

I had the same error. I had to change the name of the StarShip Connector showing within StarShip Web: 

I believe I either clicked on the StarShip Connector name or had to click the little pencil (edit) icon to change the connector name.

I did two upgrades to 24.0.2 in the last week.  I have the same issue with both of them.  The desktop client works fine so that is the good part.  The web client is getting an error.  the connector is running and works fine.  I signed up for access to the support portal last Friday but haven;t received my credentials to the support portal yet.  When you register for credential it says it may take up to 24 hours to get access.  Well it's been 5 days now.  Wonderful.  Below and attached is the same error I am getting in the web UI on both of the upgrades I did:

OK, Simon confirmed this is what has to happen.  

Next Steps

1. Upgrade to 24.0.3 (Server & Client)
   1. You will need to Install the StarShip Web Client even if using legacy desktop
2. Contact us to let us know when the upgrade is complete so we can enable the OAuth flag on your license
   
3. Go into the Server and press REGISTRATION Update and Immediately do the UPS.com Authentication.  
   1. Otherwise, it will auto update over night, and you can't ship UPS unless you have also done the Web Portion. 
4. Follow the steps for how to authenticate your UPS account by reviewing the UPS OAuth Help - this must be done via the Web Client

OK, Simon confirmed this is what has to happen.  

Next Steps

1. Upgrade to 24.0.3 (Server & Client)
   1. You will need to Install the StarShip Web Client even if using legacy desktop
2. Contact us to let us know when the upgrade is complete so we can enable the OAuth flag on your license
   
3. Go into the Server and press REGISTRATION Update and Immediately do the UPS.com Authentication.  
   1. Otherwise, it will auto update over night, and you can't ship UPS unless you have also done the Web Portion. 
4. Follow the steps for how to authenticate your UPS account by reviewing the UPS OAuth Help - this must be done via the Web Client

Thanks @Madeline Stefanou and @Roberta Chase  Are there any timing concerns for enabling OAuth?  For example, the customer is using the desktop client during the day.  Can the OAuth authorization be made by V-Technologies without affecting the desktop clients?  Certainly don't want any issues if OAuth gets enabled but the UPS account hasn't been registered yet through the web UI.

OK, Simon confirmed this is what has to happen.  

Next Steps

1. Upgrade to 24.0.3 (Server & Client)
   1. You will need to Install the StarShip Web Client even if using legacy desktop
2. Contact us to let us know when the upgrade is complete so we can enable the OAuth flag on your license
   
3. Go into the Server and press REGISTRATION Update and Immediately do the UPS.com Authentication.  
   1. Otherwise, it will auto update over night, and you can't ship UPS unless you have also done the Web Portion. 
4. Follow the steps for how to authenticate your UPS account by reviewing the UPS OAuth Help - this must be done via the Web Client

Simon at V-Technology told me if they turn it on, nothing happens "until" you go into StarShip Server and refresh the registration; or Over Night, StarShip Auto refreshes the registration. I'm planning to do these OAuth at end of day when UPS Shipment has finished, by having V-Tech turn it on then use Server to refresh keys.  Or do it in the morning after V-Tech turns it on; before any UPS Shipments. Caroline Rua <crua@vtechnologies.com> Can turn that on in V-Tech by emailing her with the client name and serial number info. 

Thanks @Madeline Stefanou and @Roberta Chase  Are there any timing concerns for enabling OAuth?  For example, the customer is using the desktop client during the day.  Can the OAuth authorization be made by V-Technologies without affecting the desktop clients?  Certainly don't want any issues if OAuth gets enabled but the UPS account hasn't been registered yet through the web UI.

OK, Simon confirmed this is what has to happen.  

Next Steps

1. Upgrade to 24.0.3 (Server & Client)
   1. You will need to Install the StarShip Web Client even if using legacy desktop
2. Contact us to let us know when the upgrade is complete so we can enable the OAuth flag on your license
   
3. Go into the Server and press REGISTRATION Update and Immediately do the UPS.com Authentication.  
   1. Otherwise, it will auto update over night, and you can't ship UPS unless you have also done the Web Portion. 
4. Follow the steps for how to authenticate your UPS account by reviewing the UPS OAuth Help - this must be done via the Web Client

I contacted Caroline Rua at V-Technologies.  She will turn on OAuth when two conditions have been met: The web client is installed, and you have the customer's UPS login credentials and there is a UPS account added to the customer's profile.  In order words, you need to get the customer's UPS.com user name and password.  If the customer doesn't have a UPS account profile, then you need to ask them to create one.

Simon at V-Technology told me if they turn it on, nothing happens "until" you go into StarShip Server and refresh the registration; or Over Night, StarShip Auto refreshes the registration. I'm planning to do these OAuth at end of day when UPS Shipment has finished, by having V-Tech turn it on then use Server to refresh keys.  Or do it in the morning after V-Tech turns it on; before any UPS Shipments. Caroline Rua <crua@vtechnologies.com> Can turn that on in V-Tech by emailing her with the client name and serial number info. 

Thanks @Madeline Stefanou and @Roberta Chase  Are there any timing concerns for enabling OAuth?  For example, the customer is using the desktop client during the day.  Can the OAuth authorization be made by V-Technologies without affecting the desktop clients?  Certainly don't want any issues if OAuth gets enabled but the UPS account hasn't been registered yet through the web UI.

OK, Simon confirmed this is what has to happen.  

Next Steps

1. Upgrade to 24.0.3 (Server & Client)
   1. You will need to Install the StarShip Web Client even if using legacy desktop
2. Contact us to let us know when the upgrade is complete so we can enable the OAuth flag on your license
   
3. Go into the Server and press REGISTRATION Update and Immediately do the UPS.com Authentication.  
   1. Otherwise, it will auto update over night, and you can't ship UPS unless you have also done the Web Portion. 
4. Follow the steps for how to authenticate your UPS account by reviewing the UPS OAuth Help - this must be done via the Web Client

I contacted Caroline Rua at V-Technologies.  She will turn on OAuth when two conditions have been met: The web client is installed, and you have the customer's UPS login credentials and there is a UPS account added to the customer's profile.  In order words, you need to get the customer's UPS.com user name and password.  If the customer doesn't have a UPS account profile, then you need to ask them to create one.

Simon at V-Technology told me if they turn it on, nothing happens "until" you go into StarShip Server and refresh the registration; or Over Night, StarShip Auto refreshes the registration. I'm planning to do these OAuth at end of day when UPS Shipment has finished, by having V-Tech turn it on then use Server to refresh keys.  Or do it in the morning after V-Tech turns it on; before any UPS Shipments. Caroline Rua <crua@vtechnologies.com> Can turn that on in V-Tech by emailing her with the client name and serial number info. 

Thanks @Madeline Stefanou and @Roberta Chase  Are there any timing concerns for enabling OAuth?  For example, the customer is using the desktop client during the day.  Can the OAuth authorization be made by V-Technologies without affecting the desktop clients?  Certainly don't want any issues if OAuth gets enabled but the UPS account hasn't been registered yet through the web UI.

I contacted Caroline Rua at V-Technologies.  She will turn on OAuth when two conditions have been met: The web client is installed, and you have the customer's UPS login credentials and there is a UPS account added to the customer's profile.  In order words, you need to get the customer's UPS.com user name and password.  If the customer doesn't have a UPS account profile, then you need to ask them to create one.

Simon at V-Technology told me if they turn it on, nothing happens "until" you go into StarShip Server and refresh the registration; or Over Night, StarShip Auto refreshes the registration. I'm planning to do these OAuth at end of day when UPS Shipment has finished, by having V-Tech turn it on then use Server to refresh keys.  Or do it in the morning after V-Tech turns it on; before any UPS Shipments. Caroline Rua <crua@vtechnologies.com> Can turn that on in V-Tech by emailing her with the client name and serial number info. 

Thanks @Madeline Stefanou and @Roberta Chase  Are there any timing concerns for enabling OAuth?  For example, the customer is using the desktop client during the day.  Can the OAuth authorization be made by V-Technologies without affecting the desktop clients?  Certainly don't want any issues if OAuth gets enabled but the UPS account hasn't been registered yet through the web UI.

OK, Simon confirmed this is what has to happen.  

Next Steps

1. Upgrade to 24.0.3 (Server & Client)
   1. You will need to Install the StarShip Web Client even if using legacy desktop
2. Contact us to let us know when the upgrade is complete so we can enable the OAuth flag on your license
   
3. Go into the Server and press REGISTRATION Update and Immediately do the UPS.com Authentication.  
   1. Otherwise, it will auto update over night, and you can't ship UPS unless you have also done the Web Portion. 
4. Follow the steps for how to authenticate your UPS account by reviewing the UPS OAuth Help - this must be done via the Web Client

Add this to the 'We need to figure this crap out within the next two weeks" list.  I couldn't follow the V-Tech screen shots and finally found out the customer has a "CampusShip" account.  CampusShip User IDs are not supported with the APIs.  UPS advises creating a new User ID and linking it to the existing account number.  Another option is contacting the Account Executive to request they unenroll the ID from CampusShip in this scenario.  I'm not going there.

I contacted Caroline Rua at V-Technologies.  She will turn on OAuth when two conditions have been met: The web client is installed, and you have the customer's UPS login credentials and there is a UPS account added to the customer's profile.  In order words, you need to get the customer's UPS.com user name and password.  If the customer doesn't have a UPS account profile, then you need to ask them to create one.

Simon at V-Technology told me if they turn it on, nothing happens "until" you go into StarShip Server and refresh the registration; or Over Night, StarShip Auto refreshes the registration. I'm planning to do these OAuth at end of day when UPS Shipment has finished, by having V-Tech turn it on then use Server to refresh keys.  Or do it in the morning after V-Tech turns it on; before any UPS Shipments. Caroline Rua <crua@vtechnologies.com> Can turn that on in V-Tech by emailing her with the client name and serial number info. 

Thanks @Madeline Stefanou and @Roberta Chase  Are there any timing concerns for enabling OAuth?  For example, the customer is using the desktop client during the day.  Can the OAuth authorization be made by V-Technologies without affecting the desktop clients?  Certainly don't want any issues if OAuth gets enabled but the UPS account hasn't been registered yet through the web UI.

I contacted Caroline Rua at V-Technologies.  She will turn on OAuth when two conditions have been met: The web client is installed, and you have the customer's UPS login credentials and there is a UPS account added to the customer's profile.  In order words, you need to get the customer's UPS.com user name and password.  If the customer doesn't have a UPS account profile, then you need to ask them to create one.

Simon at V-Technology told me if they turn it on, nothing happens "until" you go into StarShip Server and refresh the registration; or Over Night, StarShip Auto refreshes the registration. I'm planning to do these OAuth at end of day when UPS Shipment has finished, by having V-Tech turn it on then use Server to refresh keys.  Or do it in the morning after V-Tech turns it on; before any UPS Shipments. Caroline Rua <crua@vtechnologies.com> Can turn that on in V-Tech by emailing her with the client name and serial number info. 

Thanks @Madeline Stefanou and @Roberta Chase  Are there any timing concerns for enabling OAuth?  For example, the customer is using the desktop client during the day.  Can the OAuth authorization be made by V-Technologies without affecting the desktop clients?  Certainly don't want any issues if OAuth gets enabled but the UPS account hasn't been registered yet through the web UI.

Adding More Information here for everyone:  
the UPS.com user ID and Login "MUST" have access to the area shown in this image as "Accounts and Payments".  If you log into UPS.com and do not see that feature to review Accounts and Payments, you do not have User ID and Login Credentials that will support doing the "OAuth" function.  

Adding More Information here for everyone:  
the UPS.com user ID and Login "MUST" have access to the area shown in this image as "Accounts and Payments".  If you log into UPS.com and do not see that feature to review Accounts and Payments, you do not have User ID and Login Credentials that will support doing the "OAuth" function.