Desktop version

Main > Forum > 1C:Enterprise Platform > 1C:Enterprise – Business applications platform > We get a service access error on 1C

Forum

Search UsersRules
We get a service access error on 1C
#1
Active user
Points:: 0
Joined:: Jul 28, 2015

Hi everyone, we need your help.

We try to connect a web service which is about e-archive. We can connect via C# on visual studio but when we try to connect and to get datas 1C throw an exception about is xml review error -[2,1].

here is link of web service : http://earsivtransfertest.veriban.com.tr/eArchiveTransferService.svc?wsdl

we try to connect like this :

Code
  ProxySunucu =           WSReferences.VeribanEArsiv.CreateWSProxy(ThisForm.ServiceNameSpace,
                ThisForm.ServiceName,ThisForm.PortName);
                Username    = "TEST@VERIBAN.COM";
                Password    = "123456";
                LoginResult = False;
                SessionId   = "";
                ProxySunucu.Login(Username,Password,LoginResult,SessionId);



Ours web references and visual studio example is on footer of page as images.
You may try to connect this web service because it's exists for test.

Profile
#2
Guest
Points::
Joined::

Hello, Mehmet Tuğrul SARIÇİÇEK.

Please, see an example in the Adding WebService to 1C:SB topic.

Profile
#3
Active user
Points:: 0
Joined:: Jul 28, 2015

Hi Timofey Bugaevsky,

Thank you for your interests, but this example isn't related with ours problem. We could connect and get data various kind of web services. We see via 1C 4 parameters of web services method but visual studio show 3 parameters. It gives an exception when we apply the web services method.

If you try to connect to webservices where I said first entry, you'll see. Please.

Profile
#4
Interested
Points:: 0
Joined:: Apr 5, 2012

Hi Mehmet Tuğrul SARIÇİÇEK,

Many systems develope own web service. Platforms WSProxy standards may not match with publisher system.

For example, we developed E-Fatura (online invoice) system. And meet many related situations. For example, web service definition file (?wsdl) describes that will return "A" type. But in real operation publisher system return "B" type. 1C can not accept those situations.

For solution I suggest you to use "HTTPConnection" objects.
This time you will fed up of parsing xml requests and responses. But single solution if you want use 1C Platform.

Profile
Subscribe
Users browsing this topic (guests: 1, registered: 0, hidden: 0)



© 1C LLC. All rights reserved
1C Company respects the privacy of our customers and visitors
to our Web-site.