cancel
Showing results for 
Search instead for 
Did you mean: 

"Internal TSKH Error" - can't log on

Former Member
0 Kudos

Hi

We can not complete a NW 2004 SR1 Unicode install on a v5r3 i5. The install is nearly complete but we get

FRF-00007 - Unable to open RFC

FRF-00063 - Invalid call to DB instance

When I try to logon to the system I get a box "Internal TSKH Error" but no logon screen.

Kernel & install disks & TMKSVR are all the latest version.

Previously in similar cases I logon as DDIC and run the rest of the install jobs. I know the DDIC client 000 p/w is 19920706 on USR02 and the guy who started the install says he did not get to the point where you enter DDIC p/w.

Any thoughts ?

Thanks in Advance

Matt Milne

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This sounds familiar to me. Just want to check the basic before starting the installation process: after you finished copying the contents of the installation DVDs to i5's IFS, did U decompress the ISERPACK (downloadable from SAP Support Portal) to copy the most updated codes over before starting the installation process (that started with installing TMKSVR) ?

When I installed NW2005 SR1 in July, I did not update ISERPACK (level 7 at that time IIRC) BEFORE running the installation and the process failed twice. I read SAP note and updated ISERPACK after the failures but it did not help. Turned out I needed to update the pack BEFORE starting the proceess which the SAP note did not emphasize. So I had to delete everything and started all over again. I needed to download TMKSVR fix and apply it at the same time also. I guess NW2004 may follow this same manner for fix.

Satid S.

IBM Thailand

Former Member
0 Kudos

Hi

Thanks, once I restarted using the latest install CD and latest kernel it all worked fine. The person who started the install used the original install CD and this had worked OK but the failed install started after some PTF's had been applied so I would guess that was why the later install & kernel was required.

Matt Milne

Answers (1)

Answers (1)

0 Kudos

Hi Matt,

You should look up the developer traces dev_disp, dev_w*, ... in /usr/sap/<SID>/<instance>/work for more detailed error messages, first.

Regards,

Thomas

Former Member
0 Kudos

I did check previously and it looks like some VSE0* tables are missing. Its not clear if these are created by the install program the rfc call is trying to create.

The VSEO* tables are used by MS word interfaces among other things. I have seen a lot of people post errors with the rfc call at this stage of an install but no useful solutions.

Thanks

Matt