Service Ticket request failed

Hey,
Has anyone seen this "alert" coming from the domain controllers?
Service ticket request failed
I want to false positive it out because I've investigated.
But I'd rather go to the server guys with a fix ...

Yes your understanding is correct. The recommended approach is to tune out all the unneeded raw events at the reporting device itself.
This will save both the network and MARS from unnecessary traffic. You can find more details about this error at the following:
http://support.microsoft.com/kb/824905
http://technet.microsoft.com/en-us/library/bb742435.aspx
Regards
Farrukh

Similar Messages

HTTP request failed. Error code: "500". Error message

Hi ,
When we are trying to test webservices (exposed webservice in PI) scenarios in PI box we are getting error related Adapter framework service
HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://xxxx:xxxx/AdapterFramework/rtc]"
in the RWB it is showing that
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 01d76ce0-972e-11e0-c652-b25394b91e0c(INBOUND) expired
Can any body help .
Edited by: subhaniABAP on Jun 15, 2011 11:30 AM

Hi,
If you want to resolve this error when dealing with the messages, please try the cache refresh with the link:
http://host:j2eeport/CPACache/refresh?mode=full
And also go thorugh:
- In Integration Repository/Directory go to menu Environment ->
Clear SLD Data Cache
- In R/3 go to transaction SXI_CACHE -> menu XI Runtime Cache -> Start
Complete Cache Refresh
MESSAGE EXPIRED:
Increase the value of the timeout parameter 'xiadapter.inbound.timeout.default' under Services -> 'XPI Adapter:XI'
to a higher value say '600000'.
Regards,
Caio Cagnani

SMS_WSUS_CONFIGURATION_MANAGER - MessageID 6600 - The request failed with HTTP status 503: Service Unavailable

Hi all,
knowning that there are already a lot of posts concerning above message, I have to write an additional one as I could not find a solution on the web yet.
Situation:
Windows Server 2008 forest including empty root and two child domains, one child domain does have SCCM SP1 (central primary site WND) installed on W2k8 x64 machine including WSUS 3.0 SP1 => everything is working fine.
Second child domain also contains a SCCM SP1 server (primary site HUN) running on W2k8 x64 and is defined as child site of central site WND => everything is working fine too - except Software Updates.
WSUS 3.0 SP1 installed on both SCCM servers by creating additional web site (not using "defautl web site") and configured ports 8530 and 8531 (SSL not used!). No proxy necessary/used. All WSUS 3.0 requirements for W2k8 are installed (IIS roles)
Error:
SMS_WSUS_CONFIGURATION_MANAGER - MessageID 6600:
SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "xxxx0003".
Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted.
Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.
wsusutil checkhealth =>OK
downloading updates from WSUS at central site (SUSDB and WSUS folder equal in size) =>OK
wsus admin console able to connect and configuration possible => OK
IIS ports configured within SMS are equal to those configured for WSUS website
SCCM config (using Configuration Manager Console) does look correct - ConfigMgr Software Update Point role properties and Software Update Point Component properties
wcm.log does report an error: (SCCM Log files at the end.)
"The request failed with HTTP status 503: Service Unavailable"
IIS log files of both websites (default web site and WSUS Administration website) do not show any errors.
Questions:
What else should I look at? (registyr, SUSDB content,..)
What exactly does happen during the attempt to configure the upstream server by the SMS_WSUS_Configuration_Manager component? I guess a SMS process tries to contact a webservice - would it be possible to debug in more detail ?
And finally - Who does know the solution ?
wcm.log:
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4468 GMTDATE=Mi Jul 16 10:49:47.758 2008 ISTR0="xxxx0003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
wsusctrl.log (looks fine to me - is able to connect to local WSUS !):
SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 6156 (0x180C). SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 2732 (0x0AAC)
This is a WSUS Role as WSUS registry key exists. SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Waiting for changes for 0 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Timed Out... SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
There are no unhealthy WSUS Server components on WSUS Server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully checked database connection on WSUS server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
wsyncmgr.log (as a result of being not able to configure upstream server I guess):
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:03:51.481 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:03:51 4476 (0x117C)
Sync failed: WSUS server not configured. Source: CWSyncMgr:oSync SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:08:51.636 2008 ISTR0="CWSyncMgr:oSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)

I just experienced the exact same scenario. After much digging I found that csakg6so posted a fix at
Windoows-Noob
Run Internet Explorer as the SYSTEM account (psexec -s -d -i cmd.exe & C:\Program Files\Internet Explorrer\iexplore.exe)
Go to internet options
Go to conections
Go to LAN settings
Uncheck all boxes
The original post said to reboot, but that wasn't necessary for me.
After initiating a manual Software Update sync the WCM.log and WSyncMgr.log errors do not return and new updates are synchronized.

Web Service Request Failed

Hello,
Errors in the EE 4 with RedHat ES 3.
Web Service Request Failed
The following fault was returned from the web service call:
Code HTTP
String (404)/axis/services/rpc/webtopsession
------ log -----
Starting service Tomcat-Standalone
Apache Tomcat/4.1.29
Apr 15, 2005 12:26:03 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Apr 15, 2005 12:26:03 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/86 config=null
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (404)/axis/services/rpc/webtopsession
faultActor:
faultNode:
faultDetail:
{}string: return code: 404
<html><head><title>Apache Tomcat/4.1.29 - Error
report</title><STYLE></STYLE>
</head><body><h1>HTTP Status 404 -
/axis/services/rpc/webtopsession</h1><HR size="1"
noshade><p><b>type</b> Status
report</p><p><b>message</b>
<u>/axis/services/rpc/webtopsession</u></p><p><b>description</b>
<u>The requested resource (/axis/services/rpc/webtopsession) is not
available.</u></p><HR size="1"
noshade><h3>Apache
Tomcat/4.1.29</h3></body></html>
(404)/axis/services/rpc/webtopsession
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:630)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:128)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
at
com.tarantella.tta.webservices.client.apis.apache.BaseRequest.callServiceWork(BaseRequest.java:316)
at
com.tarantella.tta.webservices.client.apis.apache.BaseRequest.callService(BaseRequest.java:213)
at
com.tarantella.tta.webservices.client.apis.apache.BaseRequest.callService(BaseRequest.java:205)
at
com.tarantella.tta.webservices.client.apis.apache.WebtopSessionRequest.startSession(WebtopSessionRequest.java:62)
at
com.tarantella.tta.webservices.client.views.SessionBean.startSession(SessionBean.java:545)
at
org.apache.jsp.sessionmanager_jsp.createNewSession(sessionmanager_jsp.java:276)
at
org.apache.jsp.sessionmanager_jsp.joinSessionByClientId(sessionmanager_jsp.java:236)
at
org.apache.jsp.sessionmanager_jsp._jspService(sessionmanager_jsp.java:619)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:575)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:498)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:822)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:483)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
com.tarantella.tta.webservices.valves.InputFilter.invoke(InputFilter.java:74)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2417)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:193)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:309)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:387)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:673)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:615)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:786)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:666)
at java.lang.Thread.run(Thread.java:534)

Hello,
We have same problem on SGD4.2 on Solaris 10 with IE HTML Client.
Do you solve it ?
How ?
Please help.
Regards.

HTTP request failed. Error code: "503". Service Unavailable in RWB and Cache Refresh

Dear Experts,,
We have MDM and PI in our landscape. We are using MDM Adapter for the integration between the two.
When we try to run the T Code SXMB_IFR, we are getting HTTP request failed error. i.e., “Error Code: 503 -- Service Unavailable”. And also the RWB communication channel is not working because of this error and we are unable to refresh the cache too because of this error.
We have checked from MDM side, and messages are flowing from ready folder but not coming into PI. We had monitored the messages using
SXMB_MONI.
We have restarted the Java Server but it’s taking too much time to restart around 12 to 15 hours & we checked after that but still facing the same issue.
Could you please help me to figure out this issue.
Thank you for your support in advance.
Thanks and Regards,
Priti.

Hi Priti,
You can check the suggestion of Jyothi Anagani
Because of J2EE application com.sap.aii.af.ms.app not active
The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
Runtime Workbench "503 Service Unavailable" Error After JSPM SP Update
Regards,
Nabendu.

Connect-SPOService : The Application ID (AppID) for which the service ticket is requested does not exist on the system.

I am trying to connect to SharePoint in my Office 365 environment by following https://support.office.com/article/Set-up-the-SharePoint-Online-Management-Shell-environment-7b931221-63e2-45cc-9ebc-30e042f17e2c and I am getting:
Connect-SPOService : The Application ID (AppID) for which the service ticket is requested does not exist on the system.
Is there some setting I need to change on the O365 side? Thanks.

Hi,
Based on your description, my understanding is that you want connect SharePoint Online using PowerShell.
Please make sure that the following software is installed.
Windows Management Framework 3.0
SharePoint Online Management Shell
And then, open the SharePoint Online Management Shell and use the Script below to test
whether it works.
$User = "[username]@[tenant].onmicrosoft.com"
$Pass = "[password]"
$creds = New-Object System.Management.Automation.PSCredential($User,(ConvertTo-SecureString $Pass -AsPlainText -Force));
Connect-SPOService -Url https://[tenant]-admin.sharepoint.com -Credential $creds
Get-SPOSite
More information:
http://blog.falchionconsulting.com/index.php/2013/01/using-powershell-to-manage-sharepoint-2013-online/
Thanks,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Dennis Guo
TechNet Community Support

SQL Server Reporting Service 2008 R2 - The request failed with HTTP status 401: Unauthorized.

I got the error "The request failed with HTTP status 401: Unauthorized." when I call the Reporting Service Web Service.
The code is very simple:
// Initialise the reporting service Web Service
this.RSWebService = new ReportingService2010();
// Pass windos authentication credentials to Web Service
this.RSWebService.Credentials = System.Net.CredentialCache.DefaultCredentials;
// List children
List<CatalogItem> reports = this.RSWebService.ListChildren(folder, false).ToList();
The SQL Server is installed on a different machine (say server A) from the Web server (say server B). We are using Windows Server 2003.
The code work fine for all the scenario below:
i) Run locally (XP) to call the web service on the sql server
ii) Provide the Network Credentials with the username, password, and domain when calling the web service
iii) If the web server and sql server is using same server (i.e. not distributed)
I'm using windows authentication and impersonation. Any idea?

Hi Raymond,
If I understand correctly, the issue only happens in the environment that the web server is different with the SQL Server Reporting Services server. This means the web server is a remote server of the Report Server. Windows Integrated authentication is used
in this case. When running the web page, the 401 error occurs.
If so, it is actually a double hop issue. The double-hop problem will usually only be an issue to those of you who write some sort of web-based code (a web application or web service) that uses impersonation.
To fix the issue, we can configure kerberos authentication for the web application and the SQL Server Reporting Services.
Below is a great article that has delivered many solutions to fix the issue you met:
http://odetocode.com/articles/216.aspx
Additionally, you can read the following article to know more about double-hop:
http://blogs.technet.com/b/askds/archive/2008/06/13/understanding-kerberos-double-hop.aspx
http://blogs.msdn.com/b/knowledgecast/archive/2007/01/31/the-double-hop-problem.aspx
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT
Thanks Jin. I believe this is the cause of the problem as well.
I tried to register the SPN but unfortunately it still doesn't work. I'm not sure whether I'm using the correct SPN name.
I have 3 reporting server instance on the SQL box. So the Web Service URL is like
http://Server:80/VirtualDirectoryDev,
http://Server:80/VirtualDirectoryTest and
http://Server:80/VirtualDirectoryStaging .
What's the SPN I need to register?
I tried
Setspn -a http/Server:80/VirtualDirectoryDev domain\account
and
Setspn -a http/aerver:80 domain\account.
But both of them are not working :(

Service Clients failing with "The request failed with HTTP status 401: Unauthorized"

Hello,
We have implemented a solution using the SSRS web service clients as produced by the WSDLs. We have deployed the application on one server, and via the code we are calling the SSRS on another server (i.e., not using ReportViewer, etc.). We do
know that the user signed in has permissions since from the same staging server the Report Manager and Reports can both be accessed and viewed. However, it's only when we run the application and attempt to execute a report on the remote SSRS server that
we get the following error:
The request failed with HTTP status 401: Unauthorized. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at AMC.AssetTracker.Reporting.ReportExecution.ReportExecutionService.LoadReport(String Report, String HistoryID) at AMC.AssetTracker.Reporting.Report.GetReportByteArray() at AMC.AssetTracker.Reporting.Report.get_ReportStream()
at AMC.AssetTracker.Reporting.Report.get_GetWebUIDisplay() at AMC.AssetTracker.UserControls.AssetTrackerMain.btnGenerate_Click(Object sender, EventArgs e)
The credentials we have tried are the DefaultCredentials. One question I have is how do you use custom credentials if neither the DefaultCredentials or the DefaultNetworkCredentials work? Also, this service call does have to go through an ISA
server before reaching the SSRS server.
Any ideas?
Thanks.

It sounds like Kerberos authentication is needed in your situation since it's not on the same box.
There is a one-hop limit with NTLM authentication.
For more info please see the link below:
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/452e9627-cd8e-4709-bdd0-fbafcf9fd719
Hope this helps!
Thanks, Michael Mei

Java GSS API - Kerberos - Receive timed out when requesting service ticket.

Hi,
I'm following the following exercises about Kerberos/JGSS-API :
http://java.sun.com/javase/6/docs/technotes/guides/security/jgss/lab/
On exercise 3, I get an exception (when requesting a service ticket) from the client side:
"+Exception in thread "main" java.security.PrivilegedActionException: GSSException: No valid credentials provided (Mechanism level: Receive timed out)
etc.+"
This seems to happen when the GSSContext.initSecContext(...) method is called.
The server side receives the client connection:
"+Waiting for incoming connection...+
+Got connection from client /xxx.xxx.x.xxx+"
But then displays the following exception:
"+Exception in thread "main" java.security.PrivilegedActionException: java.net.SocketException: Connection reset
etc.+"
I checked my KDC (win 2003 Server SP2) and added SPNs with setspn but the error remains.
Any suggestion are more than welcome !

The TGT is already present on my Client machine because it is acquired automaticaly from the KDC during the Windows opening session.
I use then JAAS to access the LSA and obtain the TGT - This doesn't need any further connection to the KDC.
But the Service Ticket is requested to the KDC by my client machine..
Here is the complete output (Client side) after I destroyed the tickets (with Kerberos MIT Leash.exe and/or kdestroy.exe ):
Debug is true storeKey false useTicketCache true useKeyTab false doNotPrompt false ticketCache is null isInitiator true KeyTab is null refreshKrb5Config is false principal is null tryFirstPass is false useFirstPass is false storePass is false clearPass is false
Acquire TGT from Cache
+>>>KinitOptions cache name is C:\Documents and Settings\user.MYDOMAIN\krb5cc_user+
+>> Acquire default native Credentials+
+>>> Obtained TGT from LSA: Credentials:+
[email protected]
server=krbtgt/[email protected]
authTime=20080529135209Z
startTime=20080529135209Z
endTime=20080530015209Z
renewTill=20080702135209Z
flags: FORWARDABLE;RENEWABLE;INITIAL;PRE-AUTHENT
EType (int): 23
Principal is [email protected]
Commit Succeeded
+Authenticated principal: [[email protected]]+
Connected to address host1/xxx.xxx.x.xxx
Found ticket for [email protected] to go to krbtgt/[email protected] expiring on Fri May 30 03:52:09 CEST 2008
Entered Krb5Context.initSecContext with state=STATE_NEW
Found ticket for [email protected] to go to krbtgt/[email protected] expiring on Fri May 30 03:52:09 CEST 2008
Service ticket not found in the subject
+>>> Credentials acquireServiceCreds: same realm+
Using builtin default etypes for default_tgs_enctypes
default etypes for default_tgs_enctypes: 3 1 23 16 17.
+>>> CksumType: sun.security.krb5.internal.crypto.RsaMd5CksumType+
+>>> EType: sun.security.krb5.internal.crypto.ArcFourHmacEType+
+>>> KrbKdcReq send: kdc=yyy.yyy.y.y UDP:88, timeout=30000, number of retries =3, #bytes=1262+
+>>> KDCCommunication: kdc=yyy.yyy.y.y UDP:88, timeout=30000,Attempt =1, #bytes=1262+
SocketTimeOutException with attempt: 1
+>>> KDCCommunication: kdc=yyy.yyy.y.y UDP:88, timeout=30000,Attempt =2, #bytes=1262+
SocketTimeOutException with attempt: 2
+>>> KDCCommunication: kdc=yyy.yyy.y.y UDP:88, timeout=30000,Attempt =3, #bytes=1262+
Exception in thread "main" java.security.PrivilegedActionException: GSSException: No valid credentials provided (Mechanism level: Receive timed out)
+     at java.security.AccessController.doPrivileged(Native Method)+
+     at javax.security.auth.Subject.doAs(Subject.java:396)+
+     at SimpleAuthzz2.loginAndAction(SimpleAuthzz2.java:56)+
+     at SimpleGssClient.main(SimpleGssClient.java:36)+
SocketTimeOutException with attempt: 3
Caused by: GSSException: No valid credentials provided (Mechanism level: Receive timed out)
+     at sun.security.jgss.krb5.Krb5Context.initSecContext(Krb5Context.java:659)+
+     at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:213)+
+     at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:158)+
+     at SimpleGssClient$GssClientAction.run(SimpleGssClient.java:121)+
+     ... 4 more+
Caused by: java.net.SocketTimeoutException: Receive timed out
+     at java.net.PlainDatagramSocketImpl.peekData(Native Method)+
+     at java.net.DatagramSocket.receive(DatagramSocket.java:662)+
+     at sun.security.krb5.internal.UDPClient.receive(UDPClient.java:77)+
+     at sun.security.krb5.KrbKdcReq$KdcCommunication.run(KrbKdcReq.java:278)+
+     at java.security.AccessController.doPrivileged(Native Method)+
+     at sun.security.krb5.KrbKdcReq.send(KrbKdcReq.java:195)+
+     at sun.security.krb5.KrbKdcReq.send(KrbKdcReq.java:140)+
+     at sun.security.krb5.KrbKdcReq.send(KrbKdcReq.java:106)+
+     at sun.security.krb5.KrbTgsReq.send(KrbTgsReq.java:215)+
+     at sun.security.krb5.internal.CredentialsUtil.serviceCreds(CredentialsUtil.java:293)+
+     at sun.security.krb5.internal.CredentialsUtil.acquireServiceCreds(CredentialsUtil.java:106)+
+     at sun.security.krb5.Credentials.acquireServiceCreds(Credentials.java:561)+
+     at sun.security.jgss.krb5.Krb5Context.initSecContext(Krb5Context.java:585)+
+     ... 7 more+
It seems like the TGT is still present in the cache, even if Leash displays "no tickets".
Meanwhile, in the KDC-server side:
-What is the correct spn to add? C:\setspn GssServer/host1 user ? (I in fact tried many possibilities)..
-Is there any other special configuration to do in the KDC ?
Thanks a lot!

My problem about SGD-- Web Service Request Failed

Web Service Request Failed
The following fault was returned from the web service call:
Code Server.NoService
String The AXIS engine could not find a target service to invoke! targetService is rpc/webtopsession

my SGD's viasion is 4.3.15
my plam is suse linux

Kerberos service ticket was requested

I got the following message in my event viewer. can anyone advise on this?
A Kerberos service ticket was requested.
Account Information:
Account Name:
Account Domain:
Logon GUID:
{00000000-0000-0000-0000-000000000000}
Service Information:
Service Name:
Service ID:
NULL SID
Network Information:
Client Address:
192.168.0.57
Client Port:
1154
Additional Information:
Ticket Options:
0x40800000
Ticket Encryption Type:
0xffffffff
Failure Code:
0x25
Transited Services:
This event is generated every time access is requested to a resource such as a computer or a Windows service. The service name indicates the resource to which access was requested.
This event can be correlated with Windows logon events by comparing the Logon GUID fields in each event. The logon event occurs on the machine that was accessed, which is often a different machine than the domain controller which issued the service ticket.
Ticket options, encryption types, and failure codes are defined in RFC 4120.
thanks,
Ashley

Yeah… Code: 0x25 Clock skew too great. Workstation’s clock too far out of sync with the DC’s. refer:http://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=4771
Best,
Howtodo

Concurrent requests failing due to Linux CUPS service

Dear all,
We have a customer running their production instance on e-business suite -11.5.10.1 with Rdbms - 10.2.0.3. It is a single-node, single-tier installation running on Redhat Linux 3 (Update-8)
Whenever, concurrent programs are submitted with Print option, the concurrent requests keep hanging and never complete. At this time, the CUPS service uses 25% of the CPU time. If we restart the CUPS service, all requests complete with warning -
lpr: unable to print file: server-error-service-unavailable
APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. An error occurred while AOL tried
to spawn the print process
Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. An error occurred while AOL tried to spawn the
print process.
The only workaround, is to run the concurrent request, without print option. But, this is not an option.
Please suggest a fix for this CUPS issue.
Thanks

Check Note: 359890.1 - Apps Print Requests Fail with lp: unable to print file: client-error-not-found (Or lp: unable to print file: server-error-service-unavailable)
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=359890.1

Request Failed : Unable to execute service method 'getHistory'

Content Server Request Failed
csUnableToRetrieveHistory Unable to execute service method 'getHistory'. The error was caused by an internally generated issue. The error has been logged.

As Fabian said, there should be more information in the Content Server logs.
Jonathan
http://jonathanhult.com

The agent service is running, but the request failed for ...

Hi!
ZCM 10.3.3 on SLES 11. HP notebook, Windows 7 Pro SP1.
When WiFi is also switched on I got yellow diamond in ZCC and error "The agent service is running, but the request failed for one or more known addresses.". What this does mean? WiFi off -- green again! =)
More thanks, Alar.

Does the address it's getting via Wireless have a path back to the ZCM server? That was my point. If your wireless is vlan'd away from the wired network, ZCM won't be able to contact it through THAT particular address and will show the yellow diamond as a result even though it communicates fine through the wired address.

Access Exchange Service From SharePoint 2013 Custom Web part getting The request failed with HTTP status 401: Unauthorized.

I want to Fill a drop down with Outlook Meeting of Current log-in user in SharePoint 2013 web part for default credentials I am using the following code
ExchangeServiceBinding binding = new ExchangeServiceBinding();
ServicePointManager.ServerCertificateValidationCallback = (sender, certificate, chain, sslPolicyErrors) => true;
binding.RequestServerVersionValue = new RequestServerVersion();
binding.RequestServerVersionValue.Version = ExchangeVersionType.Exchange2010_SP2;
binding.PreAuthenticate = true;
binding.UseDefaultCredentials = true;
binding.Credentials = CredentialCache.DefaultCredentials ;
string server = "https://*********/ews/Exchange.asmx";
binding.Url = server;
I Am Getting the Error "The request failed with HTTP status 401: Unauthorized."
but when I Replace the line
binding.Credentials = CredentialCache.DefaultCredentials ;
with
binding.Credentials = new NetworkCredential(userName, password, domain);
Its run fine. Is there any way I could able to use default credential.

Hi,
As this question is more relate to Exchange development, I suggest you post it to the corresponding forum, you will get more help and confirmed answers from there.
http://social.msdn.microsoft.com/Forums/office/en-US/home?category=exchangeserver
Best regards
Patrick Liang
TechNet Community Support

Service Ticket request failed

Similar Messages

Maybe you are looking for