Cannot log in to TAM 11

Hans Manhave · February 22, 2015, 09:02:13 PM

I would like to finally get with the times and so after lots of clean up etc. etc. I did a test install from 10.8 to 11.0. Using a Windows 7 machine as machine performing the update. Using a copy of the data.

Now I cannot log into this. The signon screen comes up, but the user/pswd combo is not accepted. What is missing?

I checked the AS KB, but even though it pops something up "cannot log in after update" that particular piece never shows. So I am stuck.

Mark · February 22, 2015, 09:25:59 PM

Have you run tamstart.exe to see if it gives you any info?

Hans Manhave · February 22, 2015, 09:42:07 PM

It gives the same error: "Invalid usercode and/or password! Please try again."

(when I type in g:\wintam\tamstart at a run prompt.)

Is this a rights issue? Am I missing a file? Am I now locked out after x-number of tries? So many things are going through my head. Glad I ran a trial first, but maybe it would not be a problem if I had performed it on the real set?

Mark · February 22, 2015, 10:00:29 PM

Ah, you might be locked out as you suggest. Do you know anyone else's credentials?

Hans Manhave · February 23, 2015, 09:08:22 AM

I have a second one set up for myself for just those situations where I lock myself out, but I didn't try that. I am pretty sure that by the third attempt I typed it correctly. It does remain a possibility though.

Mark · February 23, 2015, 10:02:54 AM

Only one way to find out.

Jan Regnier · February 23, 2015, 10:39:06 AM

Is 11 still "tamstart" vs "Tamclient"?

Mark · February 23, 2015, 10:47:48 AM

Quote from: Jan Regnier on February 23, 2015, 10:39:06 AM
Is 11 still "tamstart" vs "Tamclient"?

Jan, tamstart is a utility in TAM that will tell you when files have been last indexed and give you other information when there are errors.

Jan Regnier · February 23, 2015, 02:05:48 PM

Quote from: Mark on February 23, 2015, 10:47:48 AM
Quote from: Jan Regnier on February 23, 2015, 10:39:06 AM
Is 11 still "tamstart" vs "Tamclient"?

Jan, tamstart is a utility in TAM that will tell you when files have been last indexed and give you other information when there are errors.

I know...but at one version Tamstart is replaced with Tamclient.

Charlie Charbonneau · February 23, 2015, 02:46:48 PM

Jan, Tamclient replaced asupdate if I remember correctly. It didn't replace Tamstart.

Mark · February 23, 2015, 02:49:39 PM

Quote from: Charlie Charbonneau on February 23, 2015, 02:46:48 PM
Jan, Tamclient replaced asupdate if I remember correctly. It didn't replace Tamstart.

This is correct. ASUPDATE.exe is replaced with TamClient.exe. TamStart.exe is still there and a helpful tool.

Jan Regnier · February 23, 2015, 02:52:58 PM

OH....Yep...sorry.... Tamstart runs and checks what if anything didn't run correctly! I was confused... (LOL - many comments could be made here). I guess what I was trying to get out was should he have run tamclient to re-register files...rather than asupdate.

Charlie Charbonneau · February 23, 2015, 02:58:12 PM

It might have been the vino!

Hans Manhave · February 23, 2015, 05:28:12 PM

TAMSTART also requires login. I get "Invalid usercode and/or password! Please try again." I have tried different users and their passwords. So it must be something else. Office is closed because of weather. No idea if Applied called after we closed. It is frustrating.

Hans Manhave · February 23, 2015, 05:53:30 PM

Does one have the have the computer access rights to full access for Windows 7 and TAM 11?

Mark · February 23, 2015, 09:55:15 PM

Tam does require full rights.

Hans Manhave · February 23, 2015, 10:45:31 PM

Thank you for the helpful info. While 11.0 was installed, I ran the 12.0 update just for the fun of it. (Actually to see if it would have a problem updating and if it would some how allow me in). It upgraded without problems except that I could still not log in. I set UAC to zero or off, but that didn't appear to have any impact. I have now restored my Win7 system to a time before the testing. Maybe Applied will be so good to contact me tomorrow. I have such small windows of time each month to get this done.

Jeff Zylstra · February 24, 2015, 09:06:57 AM

Have you tried logging in as a different user such as a domain admin, and then installing from that user, and also trying to run it from that user profile? That should remove any issues of rights or permissions, and also of user profile issues. I didn't read your entire thread, but maybe log in as a different TAM user as well to further rule out issues. Just a thought.

Hans Manhave · February 25, 2015, 10:28:14 AM

After having spoken with Applied this morning, I am thinking it was an access rights issue to the security table.

I am back on the mission to move forward. Unless the snow stops me, but may continue remotely in that case. I believe I upgraded from 5.x to 6.x using gotomypc on my little ATT 8125 way back in the dark ages.

Hans Manhave · March 02, 2015, 11:08:59 AM

TAM 11.0 has been installed now. But no WindowsXP station can run it. I replaced all the WinXP stations with Win7 except for two. Now I'm looking for the improvements we can experience before I update to 12 and onward.

Will have to get with Applied about XP not liking it. KB was not helpful in resolving it.

DebAmstutz · March 02, 2015, 12:04:49 PM

We're running 11.1 on XP stations (mine being one of them). I wonder why it works for us?

Hans Manhave · March 02, 2015, 02:15:52 PM

Finally had one XP station that installed correctly. Of course, this one doesn't have the correct Office version.

Jim Jensen · March 02, 2015, 02:51:09 PM

I have an XP running 2014R2! Not for much longer, but it is doing it.

Hans Manhave · March 02, 2015, 02:56:35 PM

Quote from: Jim Jensen on March 02, 2015, 02:51:09 PM
I have an XP running 2014R2! Not for much longer, but it is doing it.

That is good to hear! I can direct my attention and funds to updating further (need a couple printers, mice, msoffice) and not get sidetracked by Windows.

Amazingly, every single Windows7 machine I installed had some different situation. Even if they were all the same model (except 1), same order, same equipment installed etc. Amazing. Must have been the installer/operator (i.e. me).

Bob · March 02, 2015, 03:02:34 PM

Hans make sure you run windows updates, install all updates even the unchecked ones often drivers for your PC. This has helped more times than not when working with W7. In regards to TAM have to keep track what versions of Office work with what versions of TAM. Version 11 on W7 required changing the tam shortcut when it was done loading. I think this is where you have to manually modify target/path from asupdate.exe to tamclient.exe. I think 11 still pointed asudpate.exe but for W7 think we have to change to tamclient. 12.x on it changed tamclient.exe. If I recall from memory correctly. Maybe it was for 10.x to work on W7 but I somehow think 11.x

While it's not supported in TAM2013 we are using Office 2013 just fine.

Hans Manhave · March 02, 2015, 03:15:57 PM

I wonder why every mouse in the world now has to be wireless. I need some Logitech Trackman Wheel models that work with Windows 7. We got the current ones working with XP, but that took some work. Now they are useless. I guess Logitech is not the leader they once were because they only list two mice on their website. A gaming trackball type thing which is not very handy for office work (I have one also) and then the battery operated ones. Two steps forward, one back?