SAP Support connection not established.
Dear all
When I try to connect to sap for R3 connection. It shows green icon to say the connection is ok.
and connection status will be displayed like this.
Even it shows it is connected. RFC not established and not allow to sap service support.
once I click on connect following message will be displayed.
pls provide your sudgessions.
Thanks
priyan
Dear All..
The issue is resolved. Thats because of the SAP router licence renewal issue. [expired].
It could be checked by sapgenpse get_my_name -v -n validity on sap router.
Thanks All
Similar Messages
-
Hi,
I have a SSIS package named FlushFeed4Data that copy data from a table named TableA in a database named DatabaseA located on SQL server 2005 named SQL2005 to another table named Table B in a database named DatabaseB located on a server 2012 named SQL2012.
The server SQL2005 is setup like a linked server in the server 2012. My package runs smootly: first it removes all old records in SQL2012.DatabaseB.TableB & then copy all records from SQL2005.DatabaseA.TableA to SQL2012.DatabaseB.TableB to without
any error message. It runs well both when I ran debugging in SQL Server Data Tools (Microsoft Visual Studio) & when I executed this package in SSIS of server SQL2012. However when I use a job named FlushFeed4Data to run this package, I've got error message:
Executed as user NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.5058.0 for 64 bitCopyright (C) Microsoft Corporation. Code: 0xC002F210. Source: Insert Data Execute SQL Task. Dexcription: Executing the query "Insert
Into SQL2012.B.[dbo].TableB ..." failed with the following error: "Login failed for user '[MyCompanyDomainName]\SQL2012$' ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not
set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1) ... The package execution failed. The step failed.
Please help!
Thanks
EdwardHi Athur,
Thanks so much for your reply. I'd really appreciate about that. Following the article given by your link, I got error message when trying to create proxy
sg 14529, Level 16, State 1, Procedure sp_add_proxy, Line 45
Proxy "MyCompanyDomainName\SSISProxyDemoUser" is not a valid Windows user.
USE msdb
--Create a proxy and use the same credential as created above
EXEC msdb.dbo.sp_add_proxy
@proxy_name = ',
@credential_name=N'SSISProxyCredentials',
@enabled=1
GO
So I have a question: Do I have to create a new user account that can access our network named
PS: Below are the steps I followed the article:
--Script #1 - Creating a credential to be used by proxy
USE MASTER
GO
--Drop the credential if it is already existing
IF EXISTS (SELECT 1 FROM sys.credentials WHERE name = N'SSISProxyCredentials')
BEGIN
DROP CREDENTIAL [SSISProxyCredentials]
END
GO
CREATE CREDENTIAL [SSISProxyCredentials]
WITH IDENTITY = N'MyCompanyDomainName\SSISProxyDemoUser',
SECRET = N'abcd@0987'
GO
--Script #2 - Creating a proxy account
USE msdb
GO
--Drop the proxy if it is already existing
IF EXISTS (SELECT 1 FROM msdb.dbo.sysproxies WHERE name = N'SSISProxyDemo')
BEGIN
EXEC dbo.sp_delete_proxy
@proxy_name = N'SSISProxyDemo'
END
GO
and the rest of the script 2 hasn't been proceeded due to error:
--Create a proxy and use the same credential as created above
EXEC msdb.dbo.sp_add_proxy
@proxy_name = N'SSISProxyDemo',
@credential_name=N'SSISProxyCredentials',
@enabled=1
GO
--To enable or disable you can use this command
EXEC msdb.dbo.sp_update_proxy
@proxy_name = N'SSISProxyDemo',
@enabled = 1 --@enabled
= 0
GO
Please advise me!
Thanks,Edward -
Hi .
I was creating the pass the values t in temp tables though s sis package vs2012 .
First I was taken on executive SQL TASK.
IN EXCUTIVE SQL TASK . I was write the stored proce:
Sp;
reate procedure USP_GETEMP2333
AS
begin
Select eid,ename,dept,salary from emp
end;
create table #temp(eid int,ename varchar(20),dept varchar(20),salary int)
insert into #temp
exec USP_GETMP02333
go.
It was executive correctly.
I was taken another sequence container. In the sequence container iam creating one executive sql
In 2<sup>nd</sup> excutive sql task: sql statements is
if object_id('emp_fact_sal') is not null
drop table emp_fact_sal
select eid,ename as emp_name,sal_bar=
case when salary<=5000 then 'l'
when salary >5000 and salary<=7000 then 'm'
else
'h'
end
into emp_fact_sal from #temp.
and one falt flies it was taken to designation .
iam changing all connection properties:
in oldeb connection:
in excutive sal task properties .
delay validation is true,
and retain connection maner is also true,
and package mode is 64 bit is false.
But iwas excutive in 2<sup>nd</sup> excutive ql task .
Iam getting this type of errors,
[Execute SQL Task] Error: Executing the query " if object_id('emp_fact_sal') is not null
drop ta..." failed with the following error: "Invalid object name '#Temp'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established
correctly.
Please help meArthur suggestion works but you shouldnt even be doing this on a SQL Task.
Use a data flow task. You'll have better control over the data that is being transfered and get better performance because no staging table will be used.
Just because there are clouds in the sky it doesn't mean it isn't blue. But someone will come and argue that in addition to clouds, birds, airplanes, pollution, sunsets, daltonism and nuclear bombs, all adding different colours to the sky, this
is an undocumented behavior and should not be relied upon. -
Hello!
I'm having troubles syncing now that I have iOS7.0.4 on my iPhone 5 - I keep getting an error message stating "iTunes could not sync information to the iphone because a connection could not be established to the iphone". It's also taken home video's and some songs off the iphone which previously played & Im technically challenged at best so any help would be greatly appreciated before I throw the phone out in frustration!Hi DannyGo and welcome to the forums!
What is the firmware version of your router? You can check it by logging in the rotuer's set up page. Please check if it's the same as the version found in the downloads tab of this link.
http://homesupport.cisco.com/en-us/wireless/lbc/BEFW11S4
If not, please upgrade and reconfigure the settings. Please refer to the links below.
Checking the Linksys Router’s Firmware
Upgrading the Linksys Router's Firmware
Setting-Up a Router with Cable Internet Service - if you are on cable
Setting-Up a Router with DSL Internet Service - for DSL connections
Setting-Up the Wireless Settings on a Router
Let me know how it goes. -
Vixia HF50 - "Monitor while Out" connection not established
I have the HF50, win 7 home edition laptop and linksys wrt54gs2 v1 and trying to connect with an iphone using the "monitor while out" function.
- streaming from camera to iphone works fine, while in recording mode
- when in play mode connecting to access point works, and I can find the camera in the networks of my laptop
- When in streaming mode and trying to connect with "monitor while out", I get an error message that I have to change the port settings.
- the port is set to 80, and I entered a password (into the camera)
- I ran the checking tool that is supposed to check the system capability to use the "monitor while out" function.
- 1st check says system is not properly configured, router does not support "UPnP. I checked, the router is in fact capable of UPnP and this function is enabled
- Ran the tool again and not its saying router does not allow port mapping. I think it does, because I have some ports open for the xbox. Otherwise, I don't have much of a clue....
- I opened port 80 entering the IP of my computer and the checking tool says nothing found that would prevent me from using .....
- I opened port 80 to the IP address of the camera, however the camera won't connect allays the same error.
- I played with the settings in the router, but no success.
- running the checking tool seems to give random results between router does not provide UPnP, no port mapping and no issue found.
I suspect the issue is in the router, but I don't have any idea what to try out next.
Any help is appreciated.Yes, our psearch connections are indeed closed when an entry change triggers the DS server to write to those connections.
Now we just have to make sure there will be entry change to trigger connection clean up before our DS reaches nsslapd-maxpsearch.
Thank you. -
Cisco SMA to WSA connection not establishing
Hai, i was trying to add my cisco ironport WSA to SMA (both are in same subnet). I enabled monitoring service like
Centralized reporting and Centralized Configuration Manager in SMA. After i added the WSA ip and hostname in SMA and try to establish connection, but after several minutes it is showing timeout error.
Can you please let me know what should be the reason??? Do i need to enable anything on cisco WSA ??
Regards,
Mohamed FayzHi, actually I have the same problem, when trying to establish a connection from SMA to my WSAV (virtual web security appliance). I cannot add anymore my WSAV to my SMA. We have checked the network and connectivity is working for sure. I have also tried connecting from SMA command line to the WSAV and this is working (for ping and also a telnet to the SSH port 22 to ensure that SSH server on my WSAV is responding to my SMA and I get the prompt showing also the SSH FreeBSD version).
Here the output for telnet from SMA to WSAV port 22, which looks good:
cisco.example.com> telnet 172.44.21.5 22
Trying 172.44.21.5...
Connected to 172.44.21.5.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.4p1 FreeBSD-20100308
^]
telnet> q
Connection closed.
The connection from SMA to WSAV was working before, but just for testing purposes, I disabled WSAV from the SMA (I wanted to take some screenshots for our team on how to bind WSAV to the SMA and now I cannot establish again the connection --> same error: time out error after a few minutes). I've already reset SMA completely and reinstalled and also rebooted the both devices several times but ending again with the same timeout error ... WSAV is 8.0.5 and SMA is 8.3.6-014 (which is good due to the compatiblity matrix).
I will go on and do some testing, as I need this working again until monday...
In the meantime if you have suggestions, feel free to give me some hints :)
I'll come back to you if I would find a solution or some kind of explanation.
Greetings
Ciro -
Target connection not established
Hi,
After deployment the target table and package script is getting created in repository rather than target.
Plzs help..
ThanksYou target module has a location associated with it. When you deployed you were prompted to 'register' this location by providing the username, password, host, port and DB service name. This is where target tables and mappings will be created. I suspect you might have provided the wrong credentials when you registered your location. Test this by creating another location, associating the target module with this new location (Properties -> Location) and deploying again, this time entering the correct info when prompted to register the new location.
Nikolai -
Netviewer crashes my dell pc when trying to connect to sap support
Hi all, if this is in the wrong place, please move it.
I have had a problem that my pc crashes (blue screen) after i initiate netviewer online to connect to sap support. it is a pain because we have to use an older product and the response time is slow. i contacted netviewer directly and they sent me this fix, which has worked perfectly.
Dear customer,
Thank your for contacting Netviewer Support.
This is a known issue. When Netviewer starts on a Dell computer, the application produces a blue screen. What is causing this?
This phenomenon occurs only on Dell PCs with a preinstalled Windows operating system.
The file that causes a blue screen is no longer installed. The integrated sound card is from IDT (www.idt.com) but the file "ctAudDrv.sys" belongs to Creative Labs Advanced Audio FX Engine.
Remove the problem as follows:
Rename the file "ctAudDrv.sys" to "ctAudDrv.sys.bak" under "C:WindowsSystem32Drivers".
Restart the PC.
Download and install the appropriate audio driver from the Dell website at www.dell.com, for example: ftp://ftp.us.dell.com/audio/IDT_92HDxxx-HD-Audio_A06_R213367.exe
Für weitere technische Fragen stehe ich Ihnen gerne zur Verfügung./
Si vous avez des questions techniques n'hésitez pas à nous les poser./For further technical questions please do not hesitate to ask.
Mit freundlichen Grüßen/
Best regards/
Très cordialement/
Bakli Boussaa
Global Customer Support SpecialistHi Erik,
This is the .NET SDK forum for software development using the Crystal Reports programming runtime and nothing to do with Netviewer. No idea who looks after it...
Best to create a case in SMP and discuss with a Support Rep.
Thanks
Don
PS - not the first time the OEM Build of Windows for DELL has caused problems. I personally find it's better to update/upgrade to an off the shelf version of Windows. -
I tried to redeem a digital download copy of a movie and was presented the following error:
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Any guesses on what it is and how to resolve it?
ThanksHi
Abhilash Francis,
Could you tell us your scenario? What's your project? Is it a WCF service?
Looks like this is not a code issue.
Just from the error information,
it seems that you do not configure the service certificate very well so as to Server was unable to process request.
I am not completely sure what the real scenario is, but it might be a problem of that It is a WCF services application, please check these following articles to configure the service certificate.
If not, please feel free to let me know.
How to: Configure an IIS-hosted WCF service with SSL
Could not establish trust
relationship for the SSL/TLS secure channel
Hope this helps.
Best regards,
Kristin
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.
Click
HERE to participate the survey. -
The underlying connection was closed: Could not establish trust
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Please checkout the following code. I am just trying to login on to the web service. I have imported the certificate from IE by going to the Ondemand website.
I am using C# VS 2005
public static String Login(String loginUrlString, String userName, String password)
string p = null;
try
ServicePointManager.ServerCertificateValidationCallback = new System.Net.Security.RemoteCertificateValidationCallback(MyCertValidationCb);
HttpWebRequest myRequest = (HttpWebRequest)WebRequest.Create(loginUrlString);
HttpWebResponse myResponse;
myRequest.Method = "GET";
myRequest.Headers["UserName"] = userName;
myRequest.Headers["Password"] = password;
myRequest.AllowAutoRedirect = true;
myRequest.CookieContainer = new CookieContainer();
myRequest.ClientCertificates.Add(X509Certificate.CreateFromCertFile(@"c:\a.cer"));
// Return the response.
myResponse = (HttpWebResponse)myRequest.GetResponse();
// retrieve session id
char[] sep = { ';' };
String[] headers = myResponse.Headers["Set-Cookie"].Split(sep);
for (int i = 0; i <= headers.Length - 1; i++)
if (headers.StartsWith("JSESSIONID"))
sep[0] = '=';
SessionID = headers[i].Split(sep)[1];
break;
myResponse.Close();
p = sep.ToString();
catch (Exception e)
MessageBox.Show(e.Message);
return p;
public static bool MyCertValidationCb(
object sender,
X509Certificate certificate,
X509Chain chain,
SslPolicyErrors sslPolicyErrors)
if ((sslPolicyErrors & SslPolicyErrors.RemoteCertificateChainErrors)
== SslPolicyErrors.RemoteCertificateChainErrors)
return false;
else if ((sslPolicyErrors & SslPolicyErrors.RemoteCertificateNameMismatch)
== SslPolicyErrors.RemoteCertificateNameMismatch)
Zone z;
z = Zone.CreateFromUrl(((HttpWebRequest)sender).RequestUri.ToString());
if (z.SecurityZone == System.Security.SecurityZone.Intranet
|| z.SecurityZone == System.Security.SecurityZone.MyComputer)
return true;
return false;
return false;Hi
Abhilash Francis,
Could you tell us your scenario? What's your project? Is it a WCF service?
Looks like this is not a code issue.
Just from the error information,
it seems that you do not configure the service certificate very well so as to Server was unable to process request.
I am not completely sure what the real scenario is, but it might be a problem of that It is a WCF services application, please check these following articles to configure the service certificate.
If not, please feel free to let me know.
How to: Configure an IIS-hosted WCF service with SSL
Could not establish trust
relationship for the SSL/TLS secure channel
Hope this helps.
Best regards,
Kristin
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.
Click
HERE to participate the survey. -
Remote connections in SAP support portal time out
Hello, we are having a problem opening connections to our systems in the support portal and would appreciate any help and direction. This is probably a problem with our SAPRouter or firewall configuration but have been unable to identify where that problem is, and we are working closely with our network folks to try to correct. We are able to download OSS notes through SNOTE and all of the RFC's work correctly but we can't seem to keep a connection open to allow SAP support to login to our systems. The connection appears to open for about three minutes but then gives the error "Host did not respond 1-9 times" then the connection shows cancelled after about 18min. We have had a high priority incident open with SAP for the last couple of weeks but haven't got much response from them. SAP has the IP addresses of our SAPRouter and VPN correct and the routestring is correct.
SAPRouter = 216.253.195.169
VPN = 216.253.195.170
Routestring = /H/colo-sap-router.insummit.com/S/3299
We are able to ping SAP(194.117.106.129) from the saprouter server successfully. A few things I have read indicate that a simple test is that you should be able to telnet to SAP(ip above) on the configured port, 3299 but this we are not able to do and we've told this to SAP, we can telnet to port 21 but not 3299.
SAPRouter is on a Windows 2008 server OS using VPN. Attached is our saprouttab file.
Also attached is a trace.out file, and dev_rout file.
Here are the firewall ACLs:
access-list Outside extended permit ip host 216.253.195.169 host 147.204.100.142
access-list Outside extended permit ip host 147.204.2.5 host 216.253.195.169
access-list Outside extended permit ip host 216.169.212.169 host 147.204.100.142
access-list Outside extended permit ip host 194.117.106.129 any
access-list Outside extended permit ip any host 194.117.106.129
access-list Outside extended permit ip host 194.117.106.128 any
access-list Outside extended permit ip host 216.253.195.169 194.117.106.128 255.255.255.252
access-list Outside extended permit ip host 194.117.106.128 host 216.253.195.169
access-list Outside extended permit ip 194.117.106.128 255.255.255.252 host 216.253.195.169
access-list Outside extended permit ip host 194.117.106.129 host 216.253.195.169
access-list Outside extended permit ip host 216.169.212.169 194.117.106.128 255.255.255.252
Here are the routes:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.5.0.1 10.5.0.222 266
10.5.0.0 255.255.255.0 On-link 10.5.0.222 266
10.5.0.222 255.255.255.255 On-link 10.5.0.222 266
10.5.0.255 255.255.255.255 On-link 10.5.0.222 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
194.117.106.128 255.255.255.252 216.253.195.170 216.253.195.169 21
216.253.195.168 255.255.255.248 On-link 216.253.195.169 276
216.253.195.169 255.255.255.255 On-link 216.253.195.169 276
216.253.195.175 255.255.255.255 On-link 216.253.195.169 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 10.5.0.222 266
224.0.0.0 240.0.0.0 On-link 216.253.195.169 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 10.5.0.222 266
255.255.255.255 255.255.255.255 On-link 216.253.195.169 276
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
194.117.106.128 255.255.255.252 216.253.195.170 1
0.0.0.0 0.0.0.0 10.5.0.1 Default
And here is the VPN tunnel info:
6 IKE Peer: 194.39.131.167
Type : L2L Role : initiator
Rekey : no State : MM_ACTIVE
show ipsec sa peer 194.39.131.167
peer address: 194.39.131.167
Crypto map tag: cryptomap1, seq num: 15, local addr: 216.253.195.170
access-list encrypt_123_to_SAP extended permit ip host 216.253.195.169 194.117.106.128 255.255.255.252
local ident (addr/mask/prot/port): (216.253.195.169/255.255.255.255/0/0)
remote ident (addr/mask/prot/port): (194.117.106.128/255.255.255.252/0/0)
current_peer: 194.39.131.167
#pkts encaps: 459156, #pkts encrypt: 459156, #pkts digest: 459156
#pkts decaps: 65825, #pkts decrypt: 65825, #pkts verify: 65825
#pkts compressed: 0, #pkts decompressed: 0
#pkts not compressed: 459156, #pkts comp failed: 0, #pkts decomp failed: 0
#pre-frag successes: 0, #pre-frag failures: 0, #fragments created: 0
#PMTUs sent: 0, #PMTUs rcvd: 0, #decapsulated frgs needing reassembly: 0
#send errors: 0, #recv errors: 0
local crypto endpt.: 216.253.195.170, remote crypto endpt.: 194.39.131.167
path mtu 1500, ipsec overhead 58, media mtu 1500
current outbound spi: 90CB4EA0
current inbound spi : 769BBB0D
inbound esp sas:
spi: 0x769BBB0D (1989917453)
transform: esp-3des esp-md5-hmac no compression
in use settings ={L2L, Tunnel, }
slot: 0, conn_id: 20480, crypto-map: cryptomap1
sa timing: remaining key lifetime (kB/sec): (4373965/4063)
IV size: 8 bytes
replay detection support: Y
Anti replay bitmap:
0xFFFFFFFF 0xFFFFFFFF
outbound esp sas:
spi: 0x90CB4EA0 (2429243040)
transform: esp-3des esp-md5-hmac no compression
in use settings ={L2L, Tunnel, }
slot: 0, conn_id: 20480, crypto-map: cryptomap1
sa timing: remaining key lifetime (kB/sec): (4373954/4063)
IV size: 8 bytes
replay detection support: Y
Anti replay bitmap:
0x00000000 0x00000001
Again, any help and suggestions is greatly appreciated.
Thanks,
BrentHI Brent ,
I see your problem is critical !!!!
But you can have a net viewer session with SAP .
Its simple and effective way of analysing issue in run time .
SAP SMP Netviewer Instructions DE - YouTube
Netviewer
Please check above Links
Regards,
Abhishek -
SAP router connection is not working
Dear Experts,
I cannot connect my systems to SAP, getting the below error.My router is not expired and port 3299 is reachable.
SAPRouter "dev_rout" log as follows:
trc file: "dev_rout", trc level: 1, release: "720"
Wed Apr 09 15:55:51 2014
SAP Network Interface Router, Version 40.4
command line arg 0: C:\saprouter\saprouter.exe
command line arg 1: -r
command line arg 2: -W
command line arg 3: 60000
command line arg 4: -R
command line arg 5: C:\saprouter\saprouttab
command line arg 6: -K
command line arg 7: p: CN=SOLMAR, OU=0000881026, OU=SAProuter, O=SAP, C=DE
SncInit(): Initializing Secure Network Communication (SNC)
PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/64/64)
GetUserName()="Administrator" NetWkstaUser="Administrator"
SncInit(): Trying environment variable SNC_LIB as a
gssapi library name: "C:\saprouter\nt-x86_64\sapcrypto.dll".
File "C:\saprouter\nt-x86_64\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
SECUDIR="C:\saprouter\" (from $SECUDIR)
The internal Adapter for the loaded GSS-API mechanism identifies as:
Internal SNC-Adapter (Rev 1.0) to SAPCRYPTOLIB
Product Version = SAPCRYPTOLIB 5.5.5C pl36 (Jul 3 2013) MT,[aesni],NB
main: pid = 3656, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: 'C:\saprouter\saprouttab'
Wed Apr 09 16:00:49 2014
NiHLGetHostName: to get 192.168.4.69 succeeded in 4660ms (tl=2000ms)
Wed Apr 09 16:00:50 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:13 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:24 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:25 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:27 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:08:16 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:11:42 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:10 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:11 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:04 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:55:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:37 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:38 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:39 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:58:15 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
SAPRoutab:
P * * *
P 192.168.0.96 194.117.106.129 3299
P 192.168.0.96 194.117.106.129 *
# SNC-connection from and to SAP
#KT "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 194.117.106.129 *
# SNC-connection from SAP to local R/3-System for Support
#KP "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 192.168.* 32*
P * 194.117.106.129 *
P 127.0.0.1 194.117.106.129 3299
P * * *
P sapserv1 192.168.0.165 3389
P sapserv1 192.168.0.96 3389
P sapserv1 192.168.0.162 3389
SAPOSS Screens:Hi Philip
This looks fine. Just click on change and save again , it will automatically create SAPOSS RFC, u can see that in TX; SM59,
seems you Public IP : 192.168.0.96
The entry that you maintained in the sapsouttab was:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.0.96, 3200
you supposed to maintain the IP Address of the server that you opening the connection.not the router IP(192.168.0.96,)
make sure it looks like the below:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <IP Address of the server that you working with RFC>, 3200
Please follow this:
1.Maintain then correct entries in the saprouttab
2.restart the saprouter
3.Delete RFC: SAPOSS from TX:SM59
4. Recreate the RFC: SAPOSS from OSS1 after deleting that from SM59..
5.Go to TX: SM59 and open the RFC:SAPOSS and go to technical setting tab: and make sure that the string looks ok and make sence(if requied copy the string frm the anotherserver where the RFC:SAPOSS is workingalready) and go to log on security tab and reenter the password of the user:OSS_RFC as CPIC (all in Capital letters)
save it and test.
please send me the screen shots of saproutab and screen shot of the SAPOSS RFC from SM59 and error screen shot.
hope it clarifies the now.
Kind Regards,
Phaneendra kakani -
Hi all,
I've been trying to update my Jailbroken iPhone 4 to ios6 but, unfortunately, I keep getting the "could not establish a secure connection to the device" when connecting it to iTunes. I've tried updating "over the air" but this flags up an error too. Finally, I can't restore to a previous backup because, the backups I previously had, were stored on my old (broken) computer.
CAn anyone help? Any suggestions would be greatly appreciated!
Thanks,
Rakesh.You jailbroke your phone.
Only google may help now.
You'll find no help here.
If Haiku you don't like,
Then to Google you should hike,
You jailbroke your phone,
Now on these forums you are alone,
'Tis a day of no cheer,
For we cannot help here.
In non-poem; You jailbroke your phone, which is not support by Apple, meaning updates will not work on it as they would if you were running official software.
As per the ToC for the device, and for these Discussion Boards (both you agreed too), you will not get support either from the discussion board, or from Apple directly.
Your best bet is to Google for help and learn a valuable lesson; Jailbreaking can definitely brick your phone. -
Could Not Establish Connection to AS Java with Available Profiles
Hi All,
I am installing AS Java on SAP Netweaver 7.4 SR2.
OS: Windows Server 2008r2 and DB: MSSQLSever 2012
During the installation I got the below error on 28th Phase out of 29th.
"Deploy Java Components"
Below is the Error Log as extracted from SAPINST Log File
[ Error ] Could not establish connection to AS Java on [WIN-9OD90N7C:50204]. Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [WIN-9OD90N7C:50204]. Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:386)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.
at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:64)
at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:39)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:298)
... 14 more
Thanks and Regards
AnuragHi Anurag
Could you refer the SAP Notes for your issue
1571274 - Cannot connect to server using message server ms://
1925352 - How to check the access points (or ports) being used by a live SAP J2EE server
BR
SS -
Can not establish connection Oracle DB
Hi PI Gurus,
We have a sender JDBC CC, its working absolutely fine in PI dev.
when I check this CC in PI Qality it is giving me error as:
Error during database connection to the database URL 'jdbc:oracle:thin:@204.145.15.141:1521:PERM' using the JDBC driver 'oracle.jdbc.driver.Oracledriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Can not establish connection:: SAPClassNotFoundException: oracle.jdbc.driver.Oracledriver'
It clearly says that driver is not installed, thats why connection is not getting established. Our BASIS team installed the drivers twice copied from Dev systems, still the same error is coming.
Can anyone throw some light on this, is any problem with the version?
Thanks,
KrishnaHi Krishna,
Can you check two things:
1. whether the host name of the jdbc server u are tryin to access is present in the PI Quality system hosts file
2. Whether connectivity port is correctly opened with the jdbc server, i.e connectivity exists and is tested.
Regards,
Souvik
Maybe you are looking for
-
HP LASERJET SERIES 1200 ( EXTRA FEATURES NOT WORKING WITH MAC OSX 10.10)
I presently have a HP LASERJET PRINTER 1200 SERIES that I had been using my APPLE MAC. The MAC OS was upgraded recently to Yosmite MAC 10.10 I can still print.... however the extra features as double sided printing is lost. I have tried reloa
-
I'm preparing a "Windows 8.1 Update" OS deployment in SCCM and have encountered an issue. Here's what I did: Downloaded SW_DVD9_SA_Win_Ent_8.1_64BIT_English_-2_MLF_X19-49847.ISO from the Volume Licensing site Extracted install.wim from the ISO Mounte
-
How to upload a Word doc from MacBook to iCloud?
How to upload a Word doc from MacBook to iCloud?
-
How to retrieve data from a bad HDD off of a L755?
I have a L755-S5162 Satellite. Recently the HDD went bad. It is a Toshiba 640gb SATA drive. BIOS won't see it at all, nor will the BIOS of my desktop when I conenct it to the desktop. When connected however, it sees power and I can hear it spin, but
-
I am trying to purchase a monitor that will work with a MacBook Pro Retina (current model) and I am completely confused. I've seen people like the Dell Ultras or hate them. People complaining about lag time, etc. I just want a display that will give