Failing to  retrieve the WEBpage

Hi,
I want to get a Webpage back thru my java code...but its getting some exceptions and not really working...
public class Urlconn {
public static void main(String args[]){
try{
URL url=new URL("http://java.sun.com");
URLConnection conn=url.openConnection();
BufferedReader in=new BufferedReader(new InputStreamReader(conn.getInputStream()));
String inputLine;
while((inputLine=in.readLine())!=null)
System.out.println(inputLine);
in.close();
}catch(Exception e){
e.printStackTrace();
can anyone please help ?The error its showing is socket connect exception..
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
at sun.net.www.http.HttpClient.New(HttpClient.java:287)
at sun.net.www.http.HttpClient.New(HttpClient.java:299)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:792)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:744)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:669)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:913)

okkk...
Wat i want to mean is that I want to open the page in a browser...My intention is not only to get the webpage html source code in my inputstream...i want to display teh webpage itself in a browser when i execute this code with all its images and watsoever...Can you suggest please how shud i proceed?

Similar Messages

  • Explorer error "Failed to retrieve the Information Spaces list." from HANA

    I am getting this dumb error "Failed to retrieve the Information Spaces list. // Request timed out" in Explorer's "Manage Spaces" area every time I click on the analytic view listed under my HANA sources of the Explorer. So, my HANA source is visible, and analytic views are visible in Explorer as well, but I cannot get any Information Space created because of the error, and I could not find the error and its causes in Explorer docs.
    I already
    - upgraded HANA db to Rev 18 (for some reasons I cannot u[grade this system to SPS3 yet) and BIP and Explorer 4.0 are on the latest Patch 8 of SP2.
    - configured connection using IDT defined connection,
    - restarted servers in CMS already 100s of times.
    There is enough free space on the BO server's drive: 33GB. BO is a single server based on Win2008 R2 SP1 with 40GB RAM.
    Any ideas what else I can do to get rid of this issue? It is a test server, so I cannot open customer msg to SAP Support.
    Thanks,
    -Vitaliy

    Try increasing the timeout under
    ..\SAP BusinessObjects\Tomcat6\webapps\explorer\WEB-INF\classes\ default.settings.properties
    from
    request.timeout=60
    to
    request.timeout=600

  • Failed to retrieve the data source in Business Objects Explorer

    I have built a universe with Designer suits and separate measurements of paramentros and bound by, ran on Web Intelligence, but when I try to use the Business Objects Explorer is reported the following message:
    Failed to retrieve the data source details.
    The creation of the data source object tree failed
    What should I do?

    There are two OSS notes about this error ;
    1411433
    1363777
    Also you can take a look at this service pack
    http://ftp1.businessobjects.com/outgoing/CMS/crXIwin_en_sp3.pdf
    cheers
    Tansu
    Edited by: tansu aksu on Jan 25, 2011 5:03 PM

  • Fail to retrieve the logon ticket,please contact the administrator

    I Still get an error "Fail to retrieve the logon ticket,please contact the administrator"
    here is my status
    1. Set the values "2" for login/create_sso2_ticket and "1" for login/accept_sso2_ticket in DEFAULT profile at RZ10.
    2. Current configurationn status is GREEN from /irj/servlet/prt/portal/prtroot/com.sap.ip.bi.supportdesk.default
    3. Xcelsius 2008 SP3 Fp 6
    4. SAP GUI 7.2
    5. BW 7.02 sp8
    6. Kernel Version:  7.02 PatchLevel 108637
    I configured sap notes 1508663, 1400236, 1413075, 1413903, 1430575, 1083421, 937697, and so on..
    but, still got that error..
    where can i check to fix it?

    Hello,
    I'd suggest opening a message with support, it sounds like you have covered the basics.
    Note 1430575 also suggests after RZ10:
    Tick Entended Maintenance and click Change
    Add the following Parameters and their corresponding value:
    Parameter Name:    Parameter value
    login/accept_sso2_ticket   1
    login/create_sso2_ticket  2
    Restart the BW server
    Thanks,
    Ryan

  • "Fail to retrieve the logon ticket"

    Hi all,
    I am trying to connect my Dashboard to BPC and I did the following steps:
    1) SAP --> Open --> after selecting the appropriate system --> type login credentials
    2) I get the following error"Fail to retrieve the logon ticket, please contact the administrator." (Refer to attachment)
    3) I find the notes 1758340 and can only complete step 1-4.
    We cannot find any "trace" for step 5 and this is where I am stuck at.
    Can anyone suggest how we can move forward?
    or is there any workaround to connect my Dashboard to BPC?
    Thanks in advance for your help.
    Winson

    Hi WInson,
    This is related to SSO configuration.Check SAP Note 1413903
    Regards,
    Javed

  • Failed to retrieve the cube for connection (xyz).(Error:INF)

    Hello ,
    Any body faced this error (Failed to retrieve the cube for connection (xyz).(Error:INF)????
    Replication steps: Open the webi report in Launchpad-> refresh the report--> error appears.
    Component info:
    BOBJ Version: SAP BI 4.1 sp2 version 14.1.2.1121)
    Report: Webi report
    Source:BEX/CUBE
    Connection: OLAP
    BW : SAP BW 7.3
    At first i have checked the user availability ( lock or unlock)  olap connection --- locked --- hence unlocked the user from BW
    but still the issue is remains...
    What my thought is: Cube or Bex or un available..?/inactive?secured bex query?
    kindly suggest on this.
    Note : Don't have access to BW,BEX..

    Hi Subbarao,
    1. If Bex Query is greyed out, then it is not been enabled for external access.
    2. If Bex Query failed to retrieve cube for the connection, then the Cube might be removed or relocated (or) Connection fail
    Try this workaround, this connection will not be affected if you relocate the cube in BW side and also you can use any cube / data mart to access data from BW.
    Create a new secured OLAP Connection with SAP BICS Client under the SAP Netweaver BI 7.X option by providing credentials. Select "Do not specify a cube in the connection" and click finish then publish it to the BO Repository.
    Open the WEBI Report, select the Bex Query as Data source which you want to access, now you can able to retrieve the data from the desired BW Cube via BEX Query.
    Check the User Rights and Role imported into BOE Repository.
    --Raji. S

  • Data Manager - SAP NW Conn. - Error: "Fail to retrieve the logon ticket"

    Hi,
    I am using Xcelsius 2008 SP2 and I am testing the new way to connect to SAP BW. When Browsing for a BW Query, I get the error "Fail to retrieve the logon ticket". When using QaaWS, everything works fine. Does anybody know this error?
    Greetings,
    Simon.

    Hi Deepu,
    thanks for the feedback.
    Yes we have Xcelsius SP2, I checked version and it is 5.2.0.0
    How can I check whether it is applied to both ABAP and JAVA steaks?
    Today our basis team confirmed that they have implemented EHP1 SPS5. In BI system, if I go to "System" --> "Status" --> "SAP_BW" component has SP "SAPKW70105".
    Also I installed diagnosis tool in portal as you advised and all lights are green.
    Any other proposal?

  • Failed to retrieve the system DEP policy

    I've been getting this error on my Windows 8.1 Pro when I run EMET GUI. I think it's related to when I changed the apps configuration.
    I tried uninstalling/reinstalling and I get "Could not create EMET default configuration. Please run this program as an Administrator" even though I am running it as Administrator.
    Then I get this error when I run EMET GUI (tried both EMET 5.1 and 4.1 update 1 and have the same error)
    ************** Exception Text **************
    MitigationInterface.NonFatalException: Failed to retrieve the system DEP policy
       at MitigationInterface.SysMitigation_DEP..ctor(OSVERSIONINFOEX OsInfoEx, Boolean EnableUnsafeSettings)
       at MitigationInterface.SystemMitigations..ctor()
       at GraphicalApp.MainForm.MainForm_Load(Object sender, EventArgs e)
       at System.EventHandler.Invoke(Object sender, EventArgs e)
       at System.Windows.Forms.Form.OnLoad(EventArgs e)
       at DevExpress.XtraEditors.XtraForm.OnLoad(EventArgs e)
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
       at System.Windows.Forms.Control.CreateControl()
       at System.Windows.Forms.Control.WmShowWindow(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.Form.WndProc(Message& m)
       at DevExpress.XtraEditors.XtraForm.WndProc(Message& msg)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
    EMET_GUI
        Assembly Version: 5.1.5426.28434
        Win32 Version: 5.1.5426.28434
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/EMET_GUI.exe
    HelperLib
        Assembly Version: 5.1.5426.28431
        Win32 Version: 5.1.5426.28431
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/HelperLib.DLL
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    DevExpress.XtraBars.v13.2
        Assembly Version: 13.2.9.0
        Win32 Version: 13.2.9.0
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/DevExpress.XtraBars.v13.2.DLL
    DevExpress.Utils.v13.2
        Assembly Version: 13.2.9.0
        Win32 Version: 13.2.9.0
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/DevExpress.Utils.v13.2.DLL
    DevExpress.XtraEditors.v13.2
        Assembly Version: 13.2.9.0
        Win32 Version: 13.2.9.0
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/DevExpress.XtraEditors.v13.2.DLL
    DevExpress.Data.v13.2
        Assembly Version: 13.2.9.0
        Win32 Version: 13.2.9.0
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/DevExpress.Data.v13.2.DLL
    DevExpress.XtraTreeList.v13.2
        Assembly Version: 13.2.9.0
        Win32 Version: 13.2.9.0
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/DevExpress.XtraTreeList.v13.2.DLL
    DevExpress.UserSkins.HighContrast
        Assembly Version: 12.2.10.0
        Win32 Version:
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/DevExpress.UserSkins.HighContrast.DLL
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    System.Data
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
    System.Data.Linq
        Assembly Version: 4.0.0.0
        Win32 Version: 4.0.30319.34209
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Data.Linq.dll
    MitigationInterface
        Assembly Version: 5.1.5426.28431
        Win32 Version: 5.1.5426.28431
        CodeBase: file:///C:/Program%20Files%20(x86)/EMET%205.1/MitigationInterface.DLL

    Hi Subbarao,
    1. If Bex Query is greyed out, then it is not been enabled for external access.
    2. If Bex Query failed to retrieve cube for the connection, then the Cube might be removed or relocated (or) Connection fail
    Try this workaround, this connection will not be affected if you relocate the cube in BW side and also you can use any cube / data mart to access data from BW.
    Create a new secured OLAP Connection with SAP BICS Client under the SAP Netweaver BI 7.X option by providing credentials. Select "Do not specify a cube in the connection" and click finish then publish it to the BO Repository.
    Open the WEBI Report, select the Bex Query as Data source which you want to access, now you can able to retrieve the data from the desired BW Cube via BEX Query.
    Check the User Rights and Role imported into BOE Repository.
    --Raji. S

  • DP's have Warning "Failed to retrieve the package list on the distribution point" - How to Clear it?

    All but one of my DP's (A new one I just created) have this Warning Message:  "Failed to retrieve the package list on the distribution point".  They all seem to be working, I can update and push new content to them.
    When I go to the smsdpmon.log, it has an error for a package, but I've since redistributed it, and it is working fine. (Items below are snips from the smsdpmon.log)
    CContentDefinition::LibraryPackagesWmi: The package data in WMI is not consistent to PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
    CContentDefinition::LibraryPackagesWmi: Package PS10011B can't be found in PkgLib SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
    CContentDefinition::LibraryPackagesWmi failed; 0x80004005 SMS_Distribution_Point_Monitoring 11/16/2013 6:00:01 PM 3920 (0x0F50)
    Failed to evaluate package PS10011B, Error code 0x80070002 SMS_Distribution_Point_Monitoring 11/16/2013 6:29:50 PM 3920 (0x0F50)
    Since then, after redistributing the package, it clears up the logs... but not the warning in Monitoring:
    Start to evaluate package share for package 'PS10011B' version 0 ... SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
    Package PS10011B is verified successfully SMS_Distribution_Point_Monitoring 11/18/2013 12:39:52 PM 868 (0x0364)
    So since everything appears to be working fine, how do I clear out that Warning, so I have nice Green Check Mark Icons in my Monitoring Tab, so when something actually does go wrong, I won't just ignore it since it's always been set to Warning?

    I'll have to review this. The script
    here, alone did not solve the my issue. Interesting that it say I do not have any inconsistencies on any my DP's now, but I run the other one on a single DP, it states I have inconsistencies still.
    $WMIPkgList = Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib | Select -ExpandProperty PackageID | Sort-Object
    $ContentLib = (Get-ItemProperty HKLM:SOFTWARE\Microsoft\SMS\DP).ContentLibraryPath
    $PkgLibPath = ($ContentLib) + "\PkgLib"
    $PkgLibList = (Get-ChildItem $PkgLibPath | Select -ExpandProperty Name | Sort-Object)
    $PkgLibList = ($PKgLibList | ForEach-Object {$_.replace(".INI","")})
    $PksinWMIButNotContentLib = Compare-Object -ReferenceObject $WMIPkgList -DifferenceObject $PKgLibList -PassThru
    ##### section 1 #######################
    Write-Host Items in WMI but not the Content Library
    Write-Host ========================================
    $PksinWMIButNotContentLib
    Foreach ($Pkg in $PksinWMIButNotContentLib){
    Get-WmiObject -Namespace Root\SCCMDP -Class SMS_PackagesInContLib -Filter "PackageID = '$Pkg'" | Remove-WmiObject -Confirm
    I wonder if the first script is not looking for INI's whereas the second one is. I verified that the INI's do exist...
    I'll run the second on all of my DP's, remove the left over INI's, and report back again next week on status.
    -Tony

  • All DPs read "Failed to retrieve the package list on the distribution point"...

    About 2 weeks ago all 10 of my DPs started reporting the following warning (roughly 2 weeks after upgrading to R2):
    "Failed to retrieve the package list on the distribution point ["Display=\\<server.FQDN>\"]MSWNET:["SMS_SITE=<code>"]\\<server.FQDN>\. Or the package list in content library doesn't match the one in WMI. Review
    smsdpmon.log for more information about this failure.
    This warning has appeared in my environment once before and I've read a number of posts regarding it. In the previous situation I found the problematic package ID recorded in smsdpmon.log and followed the standard procedure of redistributing and then proceeded
    with a validation check on the affected DP. These steps resolved the issue originally.
    This time around the package ID is not referenced in smsdpmon.log. It had the same error but the ID was not listed. Unfortunately the logs have already rolled over and I forgot to save a copy so I don't have anything to reference. I'm curious if anyone else
    has seen this behavior and what the recommended fix is. 
    As always, appreciate the help!

    I used the following process to clean up these warnings on my DPs:
    Setup content validation checks for each of my affected DPs to run every morning (previously only set to weekends). I did this so when I made a change I could validate whether or not it worked the following day. It would be great if there was a way to force
    these checks manually but I haven't found a method yet.
    After the content validation check completed I filtered through the smsdpmon.log on each affected DP. This revealed the package ID that was causing the issue.
    In my environment the package in question was not needed so I deleted it. If it is required I suspect re-distributing it would work as well.
    At this stage the problem was still not fully resolved for me. Even though I had deleted the package WMI was still inaccurate. I used this script to scrub WMI on all affected DPs and it picked up the problematic package ID:
    http://gallery.technet.microsoft.com/Powershell-script-to-fix-81dc4e69
    My content validation checks are now passing and the warnings are being cleared. YEAH!
    As a final note - After running the PS script Nickolaj posted I ran started seeing dozens of error checks on my packages (Distribution Manager failed to process package "Laptop Drivers" (package ID = XYZ00123).) After doing some research
    I found I was prone to this issue:
    Failed to start DP health monitoring task. In my case the suspect file was called "Microsoft". I moved it to another location and the errors cleared immediately.
    Hope this info is helpful to others!

  • The Messaging Engine failed to retrieve the configuration from the database. Details:"c0002a1f".

    Hi All,
    We have two BizTalk nodes, from both nodes we are getting this error from today morning, nothings has changed from application end. 
    Error : The Messaging Engine failed to retrieve the configuration from the database. Details:"c0002a1f".
    Warning : Cannot perform encryption or decryption because the secret is not available from the master secret server. See the event log for related errors.
    Can you please suggest step where need to check.
    I don't have any knowledge where the master secret file saved during installation.
    Regards
    Suman 

    Most of the time, master secret server is not backup frequency. Mostly its is done during the time when the servers have been setup. If anything changed between the time the master secret has been backed up and now, then you don't have the correct version
    of master secret file backed up. This is why its is always a good practice to backup the master secret periodically and also try restoring in any of the test server to verify the backed up file is correct and also to make us conformable in restore
    process.
    You have one option now, try restoring with the file what you have  (4 years old). If the backed version is not the correct version, then only option is to reconfigure the BizTalk.
    MSDN: How to Restore the Master Secret
    You cannot backup the master secret file now as ii could have been corrupted. That the reason we're suggesting to restore the corrupted master secret file. For your future reference, following the steps as suggested in this article to take backup of master
    secret.
    MSDN: How to Back Up the Master Secret
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Distribution Point Configuration Status - Warning - Failed to retrieve the package list on the DP.

    Hi,
    Some of our DP's have a warning (Shown with a yellow exclamation mark) that never goes away. I have run a script on the DP's that could check for inconsistency in WMI, but it found nothing. Everything seems to work fine, but it is annoying that everything
    is not green when it should be!
    The warning is:
    Failed to retrieve package list on the distribution point. Or the package list in content library doesn't match the one in WMI. Review smsdpmon.log for more information about this failure.

    Hi Peter,
    Yes I have tried to validate all content to no avail. ;(
    No help to find in smsdpmon.log, I really think it is a bug...
    Here is a small part of it:
    ]LOG]!><time="03:50:29.934-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
    <![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:29.943-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Start to evaluate package 'C010003E' version 0 ...]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:586">
    <![LOG[Report status message 0x4000094C to MP]LOG]!><time="03:50:29.969-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:29.996-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Start to evaluate package share for package 'C010003E' version 0 ...]LOG]!><time="03:50:32.510-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:629">
    <![LOG[Package C010003E is verified successfully]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:649">
    <![LOG[Report state message 0x40000950 to MP]LOG]!><time="03:50:32.512-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:889">
    <![LOG[Report Body: <ReportBody><StateMessage MessageTime="20141129025032.000000+000" SerialNumber="0"><Topic ID="C010003E" Type="901" IDType="0"/><State ID="2384" Criticality="0"/><UserParameters
    Flags="0" Count="2"><Param>C010003E</Param><Param>["Display=\\dk01dc1sscm01.local.avk.dk\"]MSWNET:["SMS_SITE=C01"]\\dk01dc1sscm01.local.avk.dk\</Param></UserParameters></StateMessage></ReportBody>
    ]LOG]!><time="03:50:32.520-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="libsmsmessaging.cpp:10858">
    <![LOG[Report status message 0x40000950 to MP]LOG]!><time="03:50:32.528-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Report status message 0x40000959 to MP]LOG]!><time="03:50:32.557-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[Report status message 0x40000952 to MP]LOG]!><time="03:50:32.582-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:983">
    <![LOG[Status message has been successfully sent to MP from remote DP]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024"
    file="smsdpmon.cpp:1051">
    <![LOG[DP monitoring finishes evaluation.]LOG]!><time="03:50:32.607-60" date="11-29-2014" component="SMS_Distribution_Point_Monitoring" context="" type="1" thread="28024" file="smsdpmon.cpp:500">

  • The Server failed to retrieve the requested data

    I used to be able to open this site with firefox. I haven't been able to open it for 2 days. It does open in internet explorer.

    This appears to be an error message which has it roots in MS DTC, Microsoft Distributed Transaction Coordinator.
    This indicates that you somewhere manage to get a distributed transaction. This could be because of two things:
    1) There are triggers on the tables that accesses linked server.
    2) Your client code dabbles with some transaction class, like TransactionScope or similar.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • There was an error while retrieving the universes from the CMS (Central Management Server). (PS 20003)

    Hi there,
    When I'm trying to manage spaces in SAP Business Objects Explorer 4.1 SP04, I'm getting the following error:
    Failed to retrieve the data source list.
    There was an error while retrieving the universes from the CMS (Central Management Server). (PS 20003)
    For input string: "false"
    I've already restart Explorer servers (Explorer Exploration Server, Explorer Indexing Server, Explorer Master Server and Explorer Search Server) and rebooted the server where Explorer is installed.
    Nothing seems to fix this error message. I'm not able to create new spaces because I cant access the sources:
    I'd appreciate some help !
    Thanks in advance

    HI Pavan,
    Admin is on the Administrators Group, which as Full Control on the Explorer Application
    I think this worked on the day the Explorer was installed (past week).
    Since them never worked.

  • EDirectory install - failed to retrieve self-signed root certificate:142

    Hi,
    My istallation has 2 NICs, public & internal.
    My tree name is IS.
    I have succesfully installed and used RedCarpet. I additionally enabled
    the Firewall and DHCP server to allow internet access to my users.
    On running Yast install for eDirectory I am given the default IP address
    of the server, this is the Public IP address - I decided that eDirectory
    was for internal use so changed IP address to internal one.
    At 50% of installation an error pops up :-
    Error
    The installation failed to retrieve the self-signed root certificate:142
    I aborted the installation.
    I retried the install using the public Ip address, it complains ports are
    already in use, I chose ignore and go ahead. Same error occurs :142.
    Your assistance and guidance would be appreciated.

    > Hi Johan,
    >
    > Thanks for sticking with me... I appreciate your time and help (believe
    > me, It's a great help..)
    >
    > I have cracked it...
    >
    > On a reboot, I chose to press F2 to get rid of the Suse Chameleon screen
    > and watched the boot process progress. I then noticed that it was unable
    > to contact my specified NTP source.
    >
    > I went into Yast Ntp client and changed my NTP source to other published
    > secondary NTP servers and all failed. I then put in the ip address of one
    > of the time servers and Bingo! ntp connected...I think I've seen this
    > before with Netware...where name resolution of the ntp server name does
    > not occur....most ntpserver administrators state they prefer you contact
    > the server by name rather than address...hmmm.....
    >
    > I then retried Yast eDirectory install and it was a breeze, as was the
    > iManager install....
    >
    > GroupWise here I come...
    >
    > Rgds.
    >
    > Stan Chelchowski
    >
    Hi, this is roy.
    had the same issue. using a supermicro with a builtin dual nic.
    disabled it and installed an old pci nic to test and it finally loaded the
    edirectory without an error.
    on another note, i am installing the NLSBS 9.0 and had to manually load
    the disk drivers since i have an adaptec 2010s raid adapter. i had
    installed suse 9.3 on the same machine earlier with absolutely no issues,
    but NLSBS is a pain. if you run red carpet and update all, then the driver
    issue returns.
    how do you get and install the service pack 2?
    thanks,
    roy

Maybe you are looking for