Hey Kjetil,
Kjetil Ree wrote:
@Chris:
When you created the virtual folder, are you sure you gave the user IIS uses the necessary read permissions?
Yes. In fact I have the folder the security permission for the relevant ApplictionPool (TMSNet40AppPool) which is inherited from the "Public" application. You can anonymously link to a file in this virtual folder and download it without issue (i.e. "http://FQDN_Of_TMS/tms/public/data/software/s52000tc6_1_1.pkg")
This virtual folder pointed to the FTP folder location (see below) but I used the URL to update the to host the System Software updates URL:
There are a lot of things that can go wrong when you do this yourself. What happens if you move the Software FTP Directory back to a subfolder of IIS, e.g. the default value of C:\Program Files (x86)\TANDBERG\TMS\wwwTMS\Public\data\SOFTWARE?
Regards,
Kjetil
I didn't actually move the FTP folder location (I can't see how as this is hardcoded into TMS). Our default location is set to:
Our biggest issue, however, is that at this moment in time we cannot raise a TAC request due to the maintenance lapsing on our TMS. As we are a not-for-profit organisation, we simply cannot afford the cost. We have a huge VCS and endpoint deployment, but whilst TMS is incredibly usfull, it has been regarding as non-essential. We use it for monitoring, software upgrades, and provisioning (although the later hasn't kicked into gear as yet), but not scheduling. I have passed this back up the management chain, but I'm not sure what will be done.
swinster70 wrote:
Yes. In fact I have the folder the security permission for the relevant ApplictionPool (TMSNet40AppPool) which is inherited from the "Public" application. You can anonymously link to a file in this virtual folder and download it without issue (i.e. "http://FQDN_Of_TMS/tms/public/data/software/s52000tc6_1_1.pkg")
It is strange that there was no SOFTWARE folder there already, the installer should have created that automatically.
On my lab TMS 14.x servers, it looks like (out of the box):
What happens if you (for temporary troubleshooting purposes) give "everyone" full control over
C:\Program Files (x86)\TANDBERG\TMS\wwwtms\public\data\SOFTWARE? That way we can rule out permission issues. Also note that it is TMS's Scheduler Service that kicks off software upgrades, so it is important that this service also can access the folder (I forgot to mention that in my earlier posts, sorry).
BTW: Your Software FTP directory path shows "Program Files", could it be that you are on a 64 bit Windows so that it should be "Program Files (x86)"? You can change it using the TMS Tools application.
Other than that, I don't really know what you should do. Reinstalling TMS — something I rarely recommend — could be a possibility, so that you let the TMS installer take care of the IIS config for you.
I'll also make sure that we make a couple of software changes to TMS. I want TMS a) to abort the upgrade process earlier if it sees that it cannot build a full URL to send to the endpoint, and b) actually log something useful when it fails ( in log-web-public.txt, and in the web UI). Tracking the issue as CSCuh50070.
-Kjetil
Kjetil Ree wrote:
@Jens:
Can you check whether the "Software FTP directory" is a location that can be reached by IIS? Unless you do some IIS magic of your own, it must be a subfolder of C:\Program Files (x86)\TANDBERG\TMS\wwwTMS\. If it isn't, I see the same symptoms as Chris sees when I try to upgrade from TC 6.1.1 to 6.1.2.
It's there, it's empty though - I put a copy of the software package there and tried to upgrade again, but no go, same error:
TMS I: provision(): tms query succeeded, length 1439
Jun 14 11:33:08 ppc appl: 2725443.93 TMS I: executor(): Found heartbeat rate 0
Jun 14 11:33:08 ppc appl: 2725443.95 TMS I: executor(): cuil-processed buffer of 618 bytes
Jun 14 11:33:08 ppc appl: 2725443.95 TMS I: provision(): ok ! heartbeat 0 ! upgrade yes ! 0 files ! 0 docs
Jun 14 11:33:08 ppc appl: 2725443.95 PROV I: provision(): software upgrade url='http://TMS FQDN/' release-key='1TC006-1-CB0BBB80'
Jun 14 11:33:08 ppc appl: 2725444.00 HTTPFB I: Queue::removeAllByCollectionId: 3
Jun 14 11:33:08 ppc appl: 2725444.04 PROV I: HttpDownloader(this=0x2272cb60): done downloading 689B (from http://TMS FQDN/ to //upgrade/pkg.tmp)
Jun 14 11:33:08 ppc appl: 2725444.04 PROV ERROR: HttpDownloader(this=0x2272cb60): download failed upgrad aborted [size:689B]
Also noticed that the TMS Software Manager does not look in that folder at all, only lists the packages sitting in
C:\Program Files\TANDBERG\TMS\wwwtms\public\data\SOFTWARE - so this could be a bit confusing.
/jens
