MI server SICF services not working

Dear All,
I installed a MI 7.0 server, I am able to logon to the ABAP stack without any hassles.But, when I test any services in SICF, it throws a page cannot be displayed. All the services are active. I tried de-activating and re-activated them, but still no good.
Any pointers would be appreciated.
Cheers!
Sandeep Tudumu

Hi,
Please check
Erecruitm "THE PAGE CANNOT BE DISPLAYED" for recruiter and candidates pages
Snote:- 1088717
V...

Similar Messages

Lion Server DNS service not working for locally created zones. Caching working fine.

OS Lion Server DNS service not working for local zones. Was fine under Snow leopard server but Lion server upgrade has severely broken my DNS and web sites. Zones look fine under Server Admin but keep getting "query failed (SERVFAIL) for xxxx at /SourceCache/bind9/bind9-42/bind9/bin/named/query.c:3921" in the logs. BTW - Server Admin cant seem to see the log file either.
Surely someone actually tested that DNS still worked on Lion?

I upgraded from Snow Leopard Server to Lion Server on day 01. I hit the same issue where, after the upgrade, my Lion Server stopped serving names for my private local domain.
I finally took a few minutes to figure out what was wrong. After turning on debug logging and looking through the logs, I found my particular issue, now resolved.
The issue I had was, when the domain initially was setup when I installed Snow Leopard Server, for some reason it created a zone just for the server (in my case, something like zone "s-01.mydomain.priv"), and a separate zone for all the other machines (zone "mydomain.priv", containing all the private IPs for my local domain). I never messed with it because it worked, but generally I would have put all of them in the same zone.
My zone "mydomain.priv" had a nameserver and mail exchanger entry for my server, s-01.mydomain.priv. I could see this in the Server Admin app on the DNS bubble, Zones tab, mydomain.priv selected, and the General Info panel. This was fine in Snow Leopard. This was failing the zone load in the updated bind for Lion Server, though. The issue was that the "mydomain.priv" zone was referencing the s-01.mydomain.priv server, which was not defined in the "mydomain.priv" zone but rather in the "s-01.mydomain.priv" zone.
My fix:
1. In Server Admin, add the server to the zone "mydomain.priv". I put an A record (Add Machine) in the "mydomain.priv" zone for my server named s-01.mydomain.priv.
2. shut down DNS on the OS X Lion Server (hit the Stop DNS button on Server Admin).
3. edit /etc/named.conf by hand, removing the specialized zones that contianed just the server. In this case, it would be the section titled 'zone "s-01.mydomain.priv"' and the section titled 'zone "3.10.1.10.in-addr.arpa"'. Your in-addr.arpa zone name will change based on whatever your server IP address was. My internal one happened to have s-01.mydomain.priv mapped to 10.1.10.3.
4. Once the specialized zones for just the server were removed, I started the DNS up again. Instead of serving four zones as it had in OS X Snow Leopard Server, it now servers two zones. And, now, it is resolving my local machines for the mydomain.priv zone.
YMMV. I did note that it wasn't totally necessary to do step 3, but I never really understood the need for the specialized domain, and keeping it around would have a copy of data that would just confuse things.
Hope that helps. That's been the only hiccup I've noticed updating to OS X Lion Server thus far.

WSUS 3.0 SP2 on Server 2008 R2 not working (no console or other access)

Hi,
In a brand new network with all 2008 R2 servers I setup WSUS. Initially I could not install the role from the Roles tool in Windows and had to install it from a downloaded file from Microsoft (which I later read is due to 2008 R2).
This ran fine for about 2 weeks, I had all the clients and workstations in groups, approving updates and installing them.. all tickety boo and then one day the console wont connect and I have not been able to get back into WSUS to do anything. I tried removing
and re-installing WSUS (both keeping the local database and then deleting it the second time) but nothing helps. My event log reports the following every 6 hours:
Event ID 13042 - Self-update is not working
Event ID 12002 - The reporting web service is not working
Event ID 12012 - The API Remoting Web Service is not working
Event ID 12032 - The Server Synchronization Web Service is not working
Event ID 12022 - The Client Web Service is not working
Event ID 12042 - The SimpleAuth Web Service is not working
Event ID 12052 - The DSS Authentication Web Service is not working
Some extra points based on what I have read:
The server DOES have .net 4.0 installed
WSUS has been removed and re-installed
All servers are 2008 R2
The server also runs Remote Desktop Services.. but aside from this is just a file and print server
Because this server (and the whole network) are brand new, standard practice is to run WSUS against the Microsoft update site and install all critical and optional updates and patches and etc..
While it was working, I can't recall installing anything that may have broken it, however typically Windows patches do not cause problems on our machines, so I do not pay too close attention to what gets installed.. Perhaps one of these updates broke WSUS?
Can anyone offer some suggestions for how to troubleshoot this and try get things moving again?
Thanks!

Hi,
> then one day the console wont connect and I have not been able to get back into WSUS to do anything.
Any error message when you launch WSUS console?
You mentioned you have Kaspersky Endpoint Security software installed on WSUS server, have you configured antivirus software to exclude WSUS content directory?
If you cannot access the WSUS console and a timeout error message appears, the CPU of the WSUS server may be at, or very close to, maximum utilization, which causes the database software to time out. If the database software times out, the WSUS console cannot
be displayed.
One way of inadvertently overtaxing your WSUS server is to have antivirus software monitor the WSUS content directory. During synchronization, the antivirus software can overload the CPU.
Please ignore WSUS content in your antivirus software and check the result.
For more information please refer to following MS articles:
Issues with the WSUS 3.0 SP2 Administration Console
http://technet.microsoft.com/en-us/library/dd939877(v=WS.10).aspx
The DSS Authentication Web Service is not working.
http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/c901eb7b-7c20-4fb8-87dd-93f128ec8703
WSUS web services not working
http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/5b443a1c-01eb-4b73-ad06-03700032bec2
Lawrence
TechNet Community Support

I would like to know why when i make a web page and test in my local browser it works fine then when i tranfer to my server i does not work fine example i used javascript to put a prompt bar on a page and it worked fine local but on server not working

how come when i make a web site and i test it in my local server it works fine when i tranfer to server certain things do not work example i used javascript to put in a prompt bar for a newsletter page at the server it did not work but at local it did also it works at MOZZILLA but not internet explorer i also have cs4 was wondering if there is a way to test a page in dreamweaver and then transfer THANK YOU X-FACTOR-MEDIA

In future, please try to make the subject line of your posts shorter. In this case the following would have been sufficient: "JavaScript works locally, but not on remote server".
Short, but meaningful subject lines make it easier for others to identify what your question is about, and often bring faster help.

"no serializer is registered..." error with a web service not working

I'm using JDeveloper 10.1.3
EJB 3.0
I'm having issues with the web service not working after I create a client for it. The web service works fine up until I generate the proxy on the other side.
ERROR An error occurred for port: {http://buslogic/}MyWebService1SoapHttpPort: no serializer is registered for (class buslogic.runtime.....
I saved the file before I added the proxy and the wsdl looks the same between the working one and the non working one. I can not pin point the when the change to the web service is occuring. It seemed to work once all the way up until I had a ADF page trying to retrieve data, another time it failed when the proxy was created.
I can get the version that I saved to work immediately after the version that does not fails.
Any help would be greatly appreciated,
Dan

I'm using JDeveloper 10.1.3
EJB 3.0
I'm having issues with the web service not working after I create a client for it. The web service works fine up until I generate the proxy on the other side.
ERROR An error occurred for port: {http://buslogic/}MyWebService1SoapHttpPort: no serializer is registered for (class buslogic.runtime.....
I saved the file before I added the proxy and the wsdl looks the same between the working one and the non working one. I can not pin point the when the change to the web service is occuring. It seemed to work once all the way up until I had a ADF page trying to retrieve data, another time it failed when the proxy was created.
I can get the version that I saved to work immediately after the version that does not fails.
Any help would be greatly appreciated,
Dan

[svn] 4226: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

[svn] 4195: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

[svn] 4193: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

I experience issue with my Verizon iPhone5s cellular service not working on 3G.

I'm experiencing issue with my Verizon iPhone5s cellular service not working on 3G but LTE works great. I tried resetting network setting, new SIM card, reset iPhone to new too. I'm have the latest carrier code of 16.0. Iphone firmware 7.1.2.
I started experiencing this when verizon started advertising XLTE.
It is very frustrating when internet does not work when I'm in 3G area. Phone calls does work though. Signal is good too.
Thank you in advance.

I would agree w you but this only happens on Iphone5S.
Iphone5 works fine. I tested this with other Iphone 5 and 5s.
To test this, go to setting/celluar/turn off "Enable LTE"

Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message:
Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2    at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    This seems also to be a SP set up issue.
Thanks a lot.

Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(3) Error for SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
(5) Error Shared Services for SharePoint Server Search
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks.

SharePoint server 2013 Search Service App on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM
was set up to access the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate
to search service app admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is
in a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem
with Search Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.
Thanks a lot.

Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

SHAREPOINT 2013 WITH SQL SERVER 2012 REPORTING SERVICES - NOT WORKING

The SQL 2012 with SP1 is installed but the Reporting Services are not working and not able to connect the Sharepoint with it.
i also TRIED TO install THE ADD-ON (rsSharePoint.msi) but it doesn't connect and show the Sharepoint Mode and cannot connect the Reporting services.
If I install the Reporting Native feature then the reporting service config displays the Instance else doesn't show and connect to the sql server.
But I am able to access the Configuration manager and TCP/IP are enabled.
I have installed SQL 2012 and Sharepoint 2013. Please revert soon.
Tks - Vinay

Reporting Service
http://msdn.microsoft.com/en-us/library/jj219068.aspx
http://blogs.msdn.com/b/biblog/archive/2012/12/04/installing-and-configuring-sql-reporting-services-on-sharepoint-2013.aspx
http://blogs.msdn.com/b/psssql/archive/2011/02/18/sharepoint-adventures-setting-up-reporting-services-with-sharepoint-integration.aspx
http://dinesql.blogspot.in/2010/06/configuring-reporting-services-2008-r2_07.html
http://www.codeproject.com/Articles/355461/Dynamically-Pointing-to-Shared-Data-Sources-on-SQL
http://www.heysharepoint.com/problems-with-sql-2012-reporting-services/
http://andrewcbancroft.com/2012/06/30/troubleshooting-sql-server-2012-reporting-services-and-sharepoint-2010-integration-part-1/
Please find the helping URL
Thanks
Jaison A
http://infomoss.blogspot.in

Internet Service Not Working, sending 404 error

Hi,
I just created an Internet Service pointing to a transaction and I published it but it is not working when I click on Start Service and the browser is opened, I know the servername and the url should be well created cause I delete the service name and change it for webgui and then it works so the hostname and port shoud be ok.
I can not see it either in the SICF transaction under the ITS path I followed the instructions in the Help Manual but is not working and can´t find why, has somebody done this that can help me out?
Thanx in Advanced!
Kind Regards,
Gerardo J

Hi Tobias,
Thank you for the Link, I have followed the steps and published the service in the SE80 Transaction, I checked the settings and are correctly pointing to internal ITS, but after I published the Service I start the SICF transaction and can not find my new Service to activate it, I´m looking in /sap/bc/gui/sap/its Path wich is the Path I have configured into Internet Transaction Server > Test Tab.
I really apreciate your help!
Kind Regards,
Gerardo J

ACS 4.2 services not working

The server is running with Windows 2003 SP2 and due to some issue it got rebooted. After reboot all services stopped working.
CSAdmin, CSMon and CSRadius hanged in Starting state and CSLog in Stopping state. When i chaged the startuptype to manual and started these services
i got " Could not start the CSAdmin service on Local computer. Error 1053 The service did not respond to the start or control request in a timely fashion "
For CSLog service it gives the error message "The CSLog service on Local Computer started and then stopped. Some service stop automatically if they have
no work to do, for example, the Performance Logs and Alerts service."
In the eventviewer it shows "The description for Event ID ( 1 ) in Source ( CiscoAAA ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: CSAdmin, Can not initialize SchemeLayer, 74."
While automatic startup type event viewer shows below error.
"The description for Event ID ( 1 ) in Source ( acs ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: *** ERROR *** Assertion failed: 103401 (9.0.0.1271)
Unable to open file (C:\Program Files\CiscoSecure ACS v4.2\CSDB\acs.db) which previously opened successfully; error = 32.The description for Event ID ( 1 ) in Source ( acs ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: *** ERROR *** Assertion failed: 103401 (9.0.0.1271)
Unable to open file (C:\Program Files\CiscoSecure ACS v4.2\CSDB\acs.db) which previously opened successfully; error = 32."
Please help me to fix this.
Thanks

Since we had no access to ACS windows server. We tried to take backup from csutil but it gave schemalayer error message.As we have AV stopped, logs files deleted from the directory, killed the stuck services from the task manager and restarted the server. If it still not allowing you to restart the services, most likely you need to take backup, uninstall the ACS server and reinstall the same version of ACS followed by restore.
~BR
Jatin Katyal
**Do rate helpful posts**

SQL Server Reporting Services not starting automatically

Hi,
I have Reporting Services configured on my SharePoint 2010 Foundation server and the service is set to start automatically under a domain account. However, the service does not in fact start automatically and requires me to manually start it otherwise when
I try to use SharePoint to read some Reports, it doesn't work. Once I start the service, it works.
Is this normal behaviour? The service will remain started until the server is restarted (Windows Updates for example). I would like the service to start automatically when needed i.e. requesting to read a Report on SharePoint site.
Many thanks

Service should start automatic then, are you using some third party firewall that could block service?
And if you are using domain account for service, make sure it has log on as a service rights on local machine.
What is your event viewer saying?
In our domain environment we had similar problem with SQL and SSRS service, when I changed form of account for starting service from
domain\account to account@domain, problem was solved. I still don't really know how this helped.

MI server SICF services not working

Similar Messages

Maybe you are looking for