• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 876 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

tidspssw not valid application

Filippo Cona
Intellectual 450 points

Hi,

I'm trying to install code composer floating licenses on our server. I followed the instructions on the wiki (working on windows XP 32 bit) and installed all the tools, but when it comes to importing the license I get the error "Unable to reread license files for vendor: tidspssw (see figure).

I tried to start the vendor from the GUI but I get the error "Unable to start vendor: tidspssw"

So I tried to start directly the executable but I get the error "tidspssw.exe is not a valid Win32 application" (see figure)

Trying to download again the tidspssw archive did not change the result.

Any suggestion?

Best regards,

Filippo

  • 0
    TI__Guru**** 168377 points

    Hi,

    I don't really know what may be happening in your case; the tidspssw.exe file is a 32-bit executable and I just re-downloaded the daemon file from the License server configuration page and re-configured my server with it. I found no errors whatsoever.

    To get additional insights you may take a look at the logs inside the directory C:\Program Files\FlexNet Publisher License Server Manager\logs

    Did you to re-import the license file (step 8 of the procedure of the Windows graphical setup procedure)? That may help fix any invalid paths pre-configured.

    You could also try to delete the cache directory (after stopping the server, of course) to see if anything corrupt may be fixed.

    I wonder if the daemon download is being corrupt by AV/Firewall software - a slim chance, though.

    The working daemon I have here has the MD5 sum as 0534dd0e9a76806b2274e8be6a599fd6 and the following datecode and size:

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 450 points

    Hi Rafael and thanks for your reply!

    Actually none of your suggestions produced any result, but it is my fault, because I indicated in my previous post the wrong Operative System: I'm working on a Windows Server 2003 32 bits... I'm really sorry for that...

    When I realized this I restarted searching the forum with new keywords and found the thread with title "(lmgrd) CreateProcess error code: 0xc1 File= tidspssw.exe".

    There you posted a link to an older version of tidspssw which (at  least in my case) is compatible with Windows Server 2003 and solved my issue.

    So I have to indirectly thank you!

    Best Regards,

    Filippo

  • 0 in reply to Filippo Cona
    TI__Guru**** 168377 points

    Filippo,

    I am glad that you are up and running again, despite my near-misses. :)

    Your post gave me another idea. I have the impression that your Windows Server copy may not have some of Microsoft's runtime Redistributable Packages installed, as hinted by this thread at Microsoft's forum. By following the suggestions in this other thread you can find which libraries are missing from the <tidspssw.exe>

    This other thread mentions a few other versions that can be downloaded from TI's servers, or directly from Microsoft at this link.

    Unfortunately I don't know how the <tidspssw.exe> daemon was built, but that may be a significant reason why <tidspssw.exe> is unable to be recognized as a win32 application in your particular system.

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 450 points
    Hi Rafael,
    thanks again for the great links!
    Since the whole thing seems to work right now (I see a promising "Full License" in licensing information of my local CCS), I'll keep everything as it is right now, but surely the links maybe useful in case something stops working, as well for other windows server 2003 users searching the forum.

    So many thanks again for your support!

    Cheers,

    Filippo