SSGD 4.31.905 and Native Client with HTTPS and firewall forwarding

Hi everyone.
I've just installed SSGD 4.31.905 on a SLES9/SP3 box and configured it as to use HTTPS connections only and firewall forwarding.
I managed to handle X509 certs as to avoid having confirmation requests on the screen on every access and everything is working fine.
Just a question: when I fire up a browser and try to connect to https://IP/sgd, the browser informs me about a potential security risk since I accessed a web server using its IP address instead of using its FQDN.
If I confirm the dialog box, access is granted and everything else works fine (and this is expected).
If I use the Native Client and try to access https://IP/tarantella, I got a "connection refused" message; if I change the URL as to read https://FQDN/tarantella, everything is fine.
So it seems the Native Client cannot connect to a secured SSGD server by using an IP/hostname differente from the one recored into the X509 cert.
Is it expected or what?
Thanks,
Rob

Looks like the native client is less forgiving when it comes to certificates. Obviously, the best way to "resolve" this is to make sure that your client devices can resolve the FQDN of the SGD server.

Similar Messages

How use to simple Java client with Https ?

Experts,
I am having some difficulties to call a https webservice on DataPower.
The following simple client has no problem to call HTTP webservice but HTTPs different story. SoapUI works just fine with Https request.
Can any one make a suggestion ? Appreciate any help !
public final static String DEFAULT_SERVER
= "https://123.123.123.123:443/Wsp";
// = "https://123.123.123.123:2048";
public final static String SOAP_ACTION
= "http://mycompany.com/Inquiry";
public static void main(String[] args) {
 String server = DEFAULT_SERVER ;
 String input1 = "123";
 String input2 = "hello";
 try {
 URL u = new URL(server);
 URLConnection uc = u.openConnection();
 HttpURLConnection connection = (HttpURLConnection) uc;
 connection.setDoOutput(true);
 connection.setDoInput(true);
 connection.setRequestMethod("POST");
 connection.setRequestProperty("SOAPAction", SOAP_ACTION);
 OutputStream out = connection.getOutputStream();
 Writer wout = new OutputStreamWriter(out);
 wout.write("<?xml version=\"1.0\" encoding=\"UTF-8\"?>");
 wout.write("<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:sam=\"http://aglc.com/sampleDp\">\r\n");
 wout.write("<soapenv:Header/>\r\n");
 wout.write("<soapenv:Body>\r\n");
 wout.write("<sam:AcordRequest>\r\n");
 wout.write("<sam:TRANSID>" + input1 + "</sam:TRANSID>\r\n");
 wout.write("<sam:TRANSBODY>" + input2 + "</sam:TRANSBODY>\r\n");
 wout.write("</sam:AcordRequest>\r\n");
 wout.write("</soapenv:Body>\r\n");
 wout.write("</soapenv:Envelope>\r\n");
 wout.flush();
 wout.close();
 String hhResponse ="";
 InputStreamReader isr = new InputStreamReader(connection.getInputStream());
 BufferedReader in = new BufferedReader(isr);
 String inputLine;
 while ((inputLine = in.readLine()) != null){
 //AIGTraceLog.log(componentName,Level.INFO,inputLine);
 hhResponse = hhResponse+inputLine+"\n";
 System.out.println(hhResponse);
 in.close();
 catch (IOException e) {
 System.err.println(e);
 }

Thanks for the reply. I think I am close, based on your instruction, I did the following but still got the same error.
C:\Program Files\Java\j2re1.4.2_13>java com.mypack.testdpws.TestDPWS
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificate not Trusted
C:\Program Files\Java\j2re1.4.2_13>keytool -import -alias testDPWS -file TestDpClSsl.crt
Enter keystore password:
Enter keystore password: password
Owner: CN=TestDpClSsl
Issuer: CN=TestDpClSsl
Serial number: 2dd2d12e
Valid from: 12/1/10 4:37 PM until: 12/1/11 4:37 PM
Certificate fingerprints:
MD5: 3A:89:FE:76:BC:30:BF:F0:87:31:F5:14:29:07:60:91
SHA1: 40:71:51:4C:84:BD:08:40:A6:7D:60:A8:A8:04:BA:09:B7:E5:C9:A4
Trust this certificate? [no]: y
Certificate was added to keystore
C:\Program Files\Java\j2re1.4.2_13>java com.mypack.testdpws.TestDPWS
javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificate not Trusted
Any idea ? or do I need to add something in the test program ?

Java proxy client with HTTP sender

I have SP15. I have sender agreement with HTTP adapter for system A and Java Proxy Cleint that send message as system A.
When I send message through Java proxy I see error:
SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: HTTP; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Server agreement found belongs to adapter HTTP; current adapter is 'XI' 
When I deleted sender agreement it worked.
Could you explain this strange behavior? Is it a bug. Sender agrement for HTTP is necessary since SP16

I have the same problem with SOAP and file adapter. I've posted this here already.
XIServer/IN_BIND_WRONG_ADPT
I have deleted the sender agreement for my soap adapter scenarios, because a sender agreement is not necessary (created by the wizard). After that the soap adapter scenarios work fine. But at scenarios with a sender file adapter you need a sender agreement.
We had the following situation:
XI Test, XI SP17, Basis SP16 --> IN_BIND_WRONG_ADPT problem
XI QA, XI SP17, Basis SP14 --> okay
XI Prod, XI SP15, Basis SP 16 --> okay
We patched our XI QA to
XI QA, XI SP17, Basis SP16
After that we have the IN_BIND_WRONG_ADPT problem at our XI QA system too.
I started a SAPP OSS call two weeks ago but got no solution till now. They checked our systems some times but with no result.
Our central SLD is on the XI Prod System. Perhaps there is a connection. But I don't want to patch my XI Prod system to SP 17, because it's the only system that works without errors.
Message was edited by: Gil Ritter

WLS 8.1.4 - Generating WebService client with HTTP 1.1 protocol

I tried to generated a web service client (Weblogic Workshop 8.1.4) from a WSDL.
When I run this client I found that it uses HTTP 1.0 protocol (from access log)
Is there a way (flag,...) to force the client to use HTTP 1.1 protocol ?
Thanks
Andrea

martin ng wrote:
any reply so far?....seems to me weblogic need to improve their support. Whenever i make a query eveything goes to Forum.Hi. I hope it's documented somewhere that these forums are not
official BEA/WebLogic support. For quick official support, open
a case with them at:
http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/support/contacts/
Joe

SQL Server Management Studio and Native Client different behaviour on delete

I have a problem with transaction containing insert and delete to same table and some select/insert/update to some other tables. Problematic table has primary key defined as combination of column1 and column2.
When two different instances using Native Client execute simultaneously this code and make inserts to table then delete part of code causes deadlock. However this doesn't happen when trying this situation in MS SQL Server Management Studio query.
Is there some option that is missing from Native Client connection string which can cause this different behaviour?

Hello,
I don't think there is a difference in the behavior. SSMS uses ADO.NET and that Provider base on the Native Client.
The difference will be more that way, when the transaction is commited and so the locks released. I guess your application keeps the transaction (much) longer open; you should commit a transaction as soon as possible to avoid long time locks and so
deadlocks.
Olaf Helper
[ Blog] [ Xing] [ MVP]

ODBC Connection problem with SQL Native Client driver with CR 11

I am having an issue connecting my crystal reports to an ODBC connection that uses the SQL Native Client driver (Version 2005.90.2047.00). My reports work fine when using the SQL Server driver (Version 2000.85.3006.00). The ODBC connection is setup to use Integrated Windows Authentication and is defaulted to go to the correct database. When I test the ODBC connection in the 'ODBC Data Source Adminstrator' it connects fine.
The reports are trying to connect to stored procedures on a SQL Server 2005 database. I can log onto the ODBC connection in CR X1. When I try to set the Datasource connection for one of my reports to the ODBC connection I created, I get the following error:
'Some tables could not be replaced, as no match was found in the new data source. Please specify the table required for any unmodified tables.'
When I drill down to the SP and try to update the datasource location of the SP directly I get the following errors:
'Data Object cannot be opened/accessed'
and
'Unknown Database Connector Error'
As I said, I don't have any problems when using the SQL Server 2000 driver. One other thing to mention, when I initially connect to the ODBC connection in CR X1 with the SQL Native Client driver, it asks for a username and password. I leave these blank since I'm using Windows Authentication.
Any advice would be appreciated.
System:
Windows XP
Service Pack 3
Crystal Reports XI:
Product Version 11.0.0.1282

Hi Jeff,
I just tried to create a new report using the native driver and there is no option to use Trusted Authentication. This would be why it's failing.
I don't believe we fully supported Native driver in Cr XI. Try downloading CR Xi R2 and install SP6 from this info:
Go to this link: http://www.sdn.sap.com/irj/boc and download the trial version of CR XI R2 and use your XI keycode, then apply the patches which you can get to by clicking on the BusinessObjects tab above, then Downloads.
Direct link to the Trial version: http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx
I tested it in R2 and the Trusted Authentication option is there so your reports should work.
Thank you
Don

Connect SQL Server 2012 from Windows Server 2003 with native client 9.0

Hi,
I currently have a setup where ETL tool Ab Intio, running on a Linux server, connects to the SQL Server 2005 through a passthrough Wintel server with Windows Server 2003 OS using SQL server native client 9.0
Now I have the requirement to upgrade the SQL server from 2005 to 2012.
My question is, will it be possible to connect to SQL server 2012 through Windows Server 2003 with native client 9.0?
As per the specs, I need native client 11.0+ to fully support SQL Server 2012, but then, as per specs, native client 11.0 doesnot run on Windows server 2003. OS upgradation is currently not on the cards.
So will it be possible to the run the basic queries we use currently, if we can connect SQL server 2012 through Windows Server 2003 with native client 9.0/10.0, without updgrading the OS of the Wintel server?
Thanking you in advance!

Hi Soumya,
Yes, you can use the SQL Server Native Client shipped with SQL Server 2005 to connect to a SQL Server 2012 instance, and there is no need to upgrade the operating system.
Regards,
Mike Yin
TechNet Community Support

ODBC functions SQLExecDirectW and SQLExecute functions return error:"DIAG [22001] [Microsoft][SQL Server Native Client 10.0]String data, right truncation (0) "

Problem Description:
ODBC functions SQLExecDirectW and SQLExecute functions return error:”DIAG [22001] [Microsoft][SQL Server Native Client 10.0]String data, right
truncation (0) “. When we enable tracing in the ODBC administrator, in the SQL.log we see that values for the arguments: ColumnSize, BufferLength, and StrLen_or_IndPtr of ODBC function SQLBindParameter are not being displayed.
Environment Used:
OS: Microsoft Windows Server 2003 R2 Standard x64 Edition.
Complier: Microsoft Visual Studio 2008 SP1 for x64.
Database: Microsoft SQL Server 2008
MDAC: Microsoft Data Access Components SDK 2.8
Note: This problem is seen only in our 64bit application. However, in 32bit
SQLExecDirectW and SQLExecute functions return successfully.
As we could not find the values of 6th, 9th and 10th arguments(ColumnSize,
BufferLength, and StrLen_or_IndPtr) passed to
SQLBindParameter in the ODBC traces for 64bit, we are not sure whether the values for the above mentioned arguments are received correctly by SQLBindParameter or not. This information would help us to debug further. So, could you please let us know why
these values are not displayed.
1)Here is the extract of the SQL.log file for 32bit where the values for SQLULEN , SQLLEN and SQLLEN* are displayed properly:
PR0CNFG 1028-15f0 ENTER SQLBindParameter
HSTMT 0x006FBDD8
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD -8 <SQL_C_WCHAR>
SWORD -9 <SQL_WVARCHAR>
SQLULEN 23
SWORD 0
PTR 0x0595EBBA
SQLLEN 46
SQLLEN * 0x05A5FB00
2)Here is the extract of the SQL.log file for 64bit where the values for SQLULEN , SQLLEN are not displayed properly and
SQLExecDirectW function return error:”DIAG
[22001] [Microsoft][SQL Server Native Client 10.0]String data, right truncation (0) “. :
PR0CNFG a78-fe4 ENTER SQLBindParameter
HSTMT 000000000431D2F0
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD -8 <SQL_C_WCHAR>
SWORD -9 <SQL_WVARCHAR>
SQLULEN SQLULEN SWORD 0
PTR 0x0000000005364EFA
SQLLEN SQLLEN
SQLLEN * SQLLEN *
PR0CNFG a78-fe4 EXIT SQLBindParameter with return code 0 (SQL_SUCCESS)
HSTMT 000000000431D2F0
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD -8 <SQL_C_WCHAR>
SWORD -9 <SQL_WVARCHAR>
SQLULEN SQLULEN SWORD 0
PTR 0x0000000005364EFA
SQLLEN SQLLEN SQLLEN *

Hi Nalsr,
From my research, I found:
"[Microsoft][ODBC SQL Server Driver]String
data right truncation" error may be returned from a call to
SQLBindParameter if the size of the string parameter being used is greater than the size of the column being compared to. In other words if the
string size of the <expression> to the left of the <comparison_operator> is less than the
string size of the <expression> to the
right, ODBC may return this error.
The resolution is to make the string size of the <expression> to the
right of the <comparison_operator> less than or equal to the
string size of the <expression> on the left.
It is difficult to track down this type of problem when third party development applications are being used. ODBC Trace can be used to help determine if this problem is occuring.
Here is an example where the customer has submitted a query "select count(*) from type1 where type1 = ?", type1 is varchar(5) and the
data type being passed by the application is char[9].
Here is the relevant portion of the trace. The following information from the "exit" of SQLDescribeParam
SWORD * 0x0095e898 (12)
UDWORD * 0x0095e880 (5)
Maps to the following with the actual value in parenthesis - SQL_VARCHAR Size 5:
SQLSMALLINT *DataTypePtr
SQLUINTEGER *ParameterSizePtr
The "exit" value from SQLBindParameter provides the following
information:
SWORD 1 <SQL_PARAM_INPUT>
SWORD 1 <SQL_C_CHAR>
SQL Data Type SWORD 12 <SQL_VARCHAR>
Parameter Size UDWORD 5
SWORD 0
Value PTR 0x0181c188
Value Buffer Size SDWORD 5
String Length SDWORD * 0x0181c103 (9)
The string length parameter is the length of the
string being bound to the parameter, in this instance there is a size mismatch which results in the SQLError and the SQLErrorW with the message "[Microsoft][ODBC SQL Server
Driver]String data
right truncation" .
Hope this could be helpful.
Best regards,
Halin Huang

RE: Native Forte Clients with Express Services

I would be very interested in hearing from anyone using Express who may
have attempted using Native Forte Clients with Express Services, especially
what problems/issues (if any) you encountered and whether you found it to
be a successful way to develop complex screens where the 'look and feel'
can't be achieved with Express alone.I wrote a general-purpose windows framework which uses Express Services for its
database access. Had I known what I was letting myself in for, I probably
wouldn't have attempted it! I started it when Express V1 was fairly new, and
Express Windows did not support the types and complexity of relationships
required by the application we were developing. I soon discovered how
difficult it is to implement a completely general framework which handles every
possible permutation. Obviously I ended up making compromises, but what we
have now meets our needs very well. We are about to upgrade to Express V2, so
the real test will be whether the framework migrates smoothly to the new
release.
If I were starting a new project now with Express V2, I don't know if I would
go down the same path. If you do, be aware of the following (based on my
experience of Express V1):
* Your design MUST obey the fundamental rules of Express Services. Your
BusinessQueries must be fired off by the correct BusinessClient subclass,
your BusinessClass attributes must be logged at the right time (depending
on which concurrency scheme you are using), and you must start and end
Express transactions (different to Forte transactions) appropriately.
* Your design needs to take into account the difference in the way Express
Services handles aggregate and non-aggregate associations.
* If you manage parent-child class relationships from your windows, you must
make sure you set and log foreign key attributes at the right time. If
the relationship is not aggregation, you must also manage the order in
which the records are saved to the database (if you use referential
integrity constraints).
* If you call Express Services directly from the windows, it is hard to
reconcile the asynchronous nature of a windows interface with the
database's requirement for things to happen in a certain order. (From
memory, there was a very good discussion in this user group last year of
what should constitute a unit of work in the windows paradigm.) If I
were doing it again, I would move all the Express-related objects and
method calls from the windows to a separate layer, which would manage
putting together the data from multiple windows, assigning foreign keys
and firing things off in the right order.
Fiona Symon
Babylon Software Pty Ltd

Hello Kevin,
Normally, it has been corrected from the last public release 2.
Hope this helps.
Daniel Nguyen
Kevin Klein wrote:
>
We had a similar problem. We reported the problem to Forte technical
support and they determined that it is a bug. I don't know if this has been
fixed in the 3.0.F release.
The Stopwatch seems to be accurate for long (several second) intervals, but
it can't be trusted for measuring short intervals.
Kevin Klein
Millennium Partners, Inc.
-----Original Message-----
From: [email protected] <[email protected]>
To: [email protected] <[email protected]>
Date: Tuesday, December 30, 1997 1:40 PM
Subject: The Forte Stopwatch
All,
At our site we are using Windows NT 4.0 clients and a Windows NT
Server with Forte 3.0.E.0.
Periodically, we use the Forte StopWatch class to measure durations for
access to data. We've noticed
a strange phenomenon, and we're not sure if it's simply circumstance or if
there's a problem. All of the
measured durations that we receive through the Split method appear to
contain either a 0 or a 9 in the
tenth-of-a-second position. For example, values of 1011 and 1912. Has
anybody noticed this?
Thank you,
Keith
Name: Kevin Klein.vcf
Part 1.2 Type: text/x-vcard
Encoding: 7bit

Report fails on CE usin stored proc as data source and Native Client driver

Iu2019m using Crystal Reports 10. I have a report with a stored procedure as data source. All my other reports using views as data source. Weu2019re upgrading db from SQL Server 2000 to 2008 and start using Native Client driver.
Thereu2019s no problem to generate this report from .rpt on my local PC. But got the following error message when generate from Crystal Enterprise:
Error Message: The table could not be found. File D:\Program Files\Crystal Decisions\Enterprise 10\Data\procSched\......reportjobserver\~tmp12c06c5641c4d50.rpt.
It looks like sth related to Native Client driver. It works if I change to use old native driver in DSN on CE server.
Any ideas/advises? Appreciated to your help!

Hello,
CR 10 does not support the MS SQL Native Driver, if you want to use OLE DB then use the MS OLE DB Provider for SQL Server up to SQL 2005. SQL 2008 does not support the MDAC version so you have to install the SQL 2008 Client tools to use the SQL Native 10 driver. CR 10 does not support that Native 10 Driver.
See this MS Kbase: http://msdn.microsoft.com/en-us/library/ms131035.aspx
Convert back to the old driver for 2005 and then use ODBC if using SQL 2008, it should work...
Don

How to associate an XA Resource Manager with a Corba Native Client?

Hello,
how is a Corba Native (C++) Client associated with an XA Resource Manager? I can't find it in the documentation.
I believe I understand how it works in a Tuxedo native client: buildclient needs "-r <rmname>" and tpinit() needs to include the group name (ubbconfig group with TMS_ORA and OPENINFO).
buildobjclient does not seem have anything like the "-r" option, and the bootstrap object does not seem to have any way to specify a group.
We have a Corba client that updates the database, enqueues into /Q and invokes a transactional Corba service. All three need to be in the same transaction. I am stuck on how to get an XA DB connection.
Thanks...
Roger
PS: The proper solution is to make the client's functionality a service and have the client invoke the service. But that causes other complications.

I got part of the answer from a different thread.
Native clients do not need a TMS_* to start a transaction. On commit/rollback they consult the Global Transaction Table (GTT) to find a TMS_* that is involved in the transaction and delegate the commit/rollback to one of those TMS_*.
For remote clients (using IIOP) the ISH handles the request from the remote client and deals with transaction management.
Roger

New Dell Server with OpenManage Essentials adds SQL Server 2012 Native Client to existing SQL Server 2008R2 in SBS 2011

Had to upgrade my server to new Dell T320. Support wanted me to install OpenManage Essentials which unfortunately installed SQL Server 2912 native client. Now I have 2 sqlserv apps running at the same time.
Is there a problem with SBS 2011 Standard running two different SQL Server native clients?
I have no idea why Dell OpenManage did not use the existing 2008R2 native client, but that is the way it is.
Can I combine or upgrade the database so they all use one and not both?
Thanks
Gerald Fay

Hi,
I have asked some who similar the SQL product, in general you can install the different version SQL client on the same operation system, but when the OpenManage Essentials
install a SQL instance on your SQL server, it will automatic upgrade same SQL component to the newer version.
For example, if your SQL server is 2008r2, you install the OpenManage Essentials built-in SQL instance which version is higher(such as 2012), by default it will automatic
upgrade the same SQL component to SQL 2012, I don’t similar with the OpenManage Essentials
tool, I think you can ask DELL® support for the further support.
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Sql Server Native Client and Office 2013 Professional Plus template

Does the Office 2013 Professional Plus template include sql server native client 10.0?
This is in response to an earlier question: https://social.msdn.microsoft.com/Forums/azure/en-US/70e91af7-586a-41ca-994e-b8378928847e/connecting-access-2013-using-preview-image-to-azure-sql-database?forum=AzureRemoteApp
Using the Office 365 trial subscription image - the sql server native client 10.0 is not included in this image.
The reason for the question is that I'd like to link an MS Access database front end to SQL Azure and it is quite helpful to have the sql server native client 10.0.
Thanks,
Dave

Hi Dave,
Unfortunately the Office 365 ProPlus (Subscription required) (Uploaded on 11/26/2014) image template
does not include the SQL Server Native Client.
As of now you would need to
create a custom image template with the required software and upload it.
I just created one a couple of days ago for a customer that had what you are requesting plus a few extras. In their case they have a custom application that they needed to connect to SQL Server on an IaaS VM so I built the custom
image to accommodate that plus other requirements.
-TP

Difference between native client and workstation client.

hi,
I am confused with the difference between native client and workstation client.In
some docs,it is said that native client is one which run on the same system as
the server,in other it is said running on other machine in the same domain.So
what about workstation client?So can anyone please helpme out in knowing this
difference?

subhash wrote:
hi,
I am confused with the difference between native client and workstation client.In
some docs,it is said that native client is one which run on the same system as
the server,in other it is said running on other machine in the same domain.So
what about workstation client?So can anyone please helpme out in knowing this
difference?The simple answer is that /WS clients are compiled with the -w option.
The complicated answer has to do with how the client connects to Tuxedo during the
tpinit(), and all subsequent traffic. A Tuxedo Domain (instance) has a Bulletin
Board, which is a chunk of shared memory with all kinds of information about Servers
and Clients. A Native Client, since it is running on the same machine that the
Bulletin Board exists on, can directly access the shared memory. However, /WS client
(also called a remote client) cannot access this shared memory. Instead, we have the
WSL server to make connections with, and then WSH processes that access the Bulletin
Board on behalf of the remote client.
So Native Clients run on the same machine as the Servers and where the Bulletin Board
is located, and have direct access to shared memory and other IPCs. Workstation
Clients/WS Client/Remote Clients (all the same thing) cannot access IPCs and have the
WSH do it on their behalf.
In NT, the Tuxedo IPC Service mimics Unix IPCs, and so all the above is still true.
Brian Douglass
Transaction Processing Solutions, Inc.
8555 W. Sahara
Suite 112
Las Vegas, NV 89117
Voice: 702-254-5485
Fax: 702-254-9449
e-mail: [email protected]
[briand.vcf]

[Microsoft][SQL Server Native Client 11.0][SQL Server]The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 'Items' (OITM) (OITM)

Dear Experts,
i am getting the below error when i was giving * (Star) to view all the items in DB
[Microsoft][SQL Server Native Client 11.0][SQL Server]The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 'Items' (OITM) (OITM)
As i was searching individually it is working fine
can any one help me how to find this..
Regards,
Meghanath.S

Dear Nithi Anandham,
i am not having any query while finding all the items in item master data i am giving find mode and in item code i was trying to type *(Star) and enter while typing enter the above issue i was facing..
Regards,
Meghanath

SSGD 4.31.905 and Native Client with HTTPS and firewall forwarding

Similar Messages

Maybe you are looking for