Client installation

[Former Member]

Hi all,

I have quite a predicament here. I have a customer where I already successfully installed SAP client on the server and could successfully login on the server itself, no sweat. That being said, the version is 8.81 PL 06.

Now the problem is, I already installed SAP client on user's workstation, but somehow I failed to login to the server. The SQL database server instance shown up in choose company form, the company database list itself also displayed. But, when I key-in the user and password and tried to login, there was error message "Internal error blablabla".

Now let me explain a little bit, I already tried to uninstall the DI API and SAP client, reinstalled the DI API and SAP client from latest patch, but with no avail. I tried to download SQL native client for SQL Server 2008 R2, installed it, but still with no avail. Most of my customer's workstation already using Windows XP SP3.

However, I tried something in my desperation to solve this problem, I installed the SQL Server itself on the user's workstation (yes, you read it right...). Nonetheless, I only installed the component "client connectivity tool" and "management studio". Actually, my first intention was to isolate the problem, whether the problem is actually revolving SQL connection or SAP related installation. But, subsequently after I installed the SQL Server with those two component, voila! the client could connect and successfully login to the SAP.

But still, this workaround is far from pretty. It is really strange and far from elegant that we need to install SQL Server on each workstations in order to connect to the server. Does anyone here could help me what installer / method actually equivalent to installation of those 2 features in SQL Server? At first, I thought SQL native client should be suffice, but apparently it is not. Frankly, that was not the first time I attempt to install SAP 8.81 on server and workstation, I already did this on my another 2 clients, somehow it only occurred on my particular customer here.

Best Regards,

Hendry Wijaya

[former_member186095 · Accepted solution]

Halo pa kabar bro ?

Is the error message internal error (-1) ... or internal error (1102) ?

you may check this :

atau:

Firstly verify if you can connect to the database with Query Analyzer/

SQL Server Management Studio with the same credentials from the same

machine.

Also verify your connection to SBO-COMMON.

Check log and Data file size (.mdf and .ldf). Truncate or shrink the

database and the log file and make sure that they are allowed to grow

unrestricted.

Check that you are specifying the correct database server type in the

logon screen:

SQL_2008 (and not SQL 2005 in case an option)

Afterwards you can kindly perform the following steps on the affected

clients:

- Firewall/Antivirus disabled

- Uninstall SAP Business One client from Add/Remove Programs

- Go to start > run type %temp%. If it is ok try deleting as many

files from here as possible

- Reboot PC

- Log as administrator

- Install SAP Business One client from B1_SHR folder

servername>B1_SHR.

atau:

this sap note

https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F...

is for internal error (-1102)

if both above solutions not solve, you can give detail problem. smoga berhasil bro

rgds,

f

[Former Member · Accepted solution]

Trims Jimmy, appreciate your input.

However, as you can read from my posting, if the problem due to firewall etc. I won't be able to connect to the server even after I installed those 2 components of SQL Server.

That being said, I already turn off the firewall, no antivirus (still, even there was exist, I won't be able to connect even after I install SQL Server on the workstation wasn't it), and routine procedure such as deleting %temp% already been done again and again.

Like my first post suggest, the problem solved simply by installing SQL Server on the workstation. I installed SQL Server Express 2008 R2 with these 2 component : client connectivity and management studio. But, the problem is, and logically you should also agree with me, it is far from elegant to perform installation of SQL Server on the workstation only to connect to SAP Server. I already installed SQL native client for SQL Server 2008 R2 but with no avail. So the question is, what installation step / action that could resolve this problem apart from installing SQL Server on each workstation?

Best Regards.

[former_member186095 · Accepted solution]

Itulah SAP bro. SAP (selalu ada problem), :).

To solve your issues, I suggest to do these steps:

1. Upgrade your PL version to latest PL of SBO 8.81 i.e. PL10

2. Check UAC level in the PC if the PC using windows 7 but it if the client PC uses xp sp3, no UAC checking is needed.

3. If the client pc still uses the XP SP3, upgrade to the windows 7 (enterprise, ultimate and professional). Just an info, the maintenance for OS XP will be end on 2014

4. log a message to sap support

Rgds,

JM7154

[Former Member · Accepted solution]

How are your users connecting to SQL - sa or trusted? have you c hecked SQL logs to see what error messages are there on connection?

[Former Member · Accepted solution]

Don't forget the notorious "Setan Aja Pusing"

What a coincidence, this thread problem looks similar to mine albeit not precisely same

[;.

Yeah, I'm gonna try to upgrade to latest version, thanks.

Best Regards,

Hendry Wijaya

[Former Member · Accepted solution]

Hi Julie,

I use sa user. Looks like I need to try to upgrade to latest version, thanks anyway for your input.

Best Regards.

[Former Member · Accepted solution]

Hi Hendry,

I just notived you are on PL06. That did have a nasty bug around client connections, so an upgrade is definitly the way to go.

[Former Member · Accepted solution]

Hi Julie,

Indeed, thanks for your input.

Best Regards,

Hendry Wijaya