Unable to connect to the Livecycle Server in CM (Non Turnkey Install)

As per the guide, I performed the following steps in the non turnkey install of LiveCycle
1) Installed the JDK 1.5.0_11
2) Copied the Jboss 4.0.3 folder from the install folder to C:\jboss
3) Created the datasource and JMS for Oracle
4) Installed the Liveycle solution components
5) Ran the Config Mgr only to configure LC
6) Copied the EAR fileds from C:\Adobe\LiveCycle8.2\ConfigurationManager\export\ to C:\jboss\..\all\deploy
7) Restarted Jboss
In the next step I when I the Config Mgr to deploy the components, I am asked to verify the connected. This is where I am stuck and I am unable to proceed. I used administrator/password as the login.
I get the following error:
"Failed to connect to the service container. Livecycle container information or login information may be invalid or the server is not running or accessible."
As this is the first install the logins are default. I don't know what I am doing wrong.
Can someone please help ?
Thanks in advance.
Aditya

Hi,
Make sure that, target server address is correct and you are able to telnet to that target server port.
Raj

Similar Messages

SSRS 2012 with SharePoint 2010: Unable to connect to the remote server

We had originally installed SSRS 2012 with SP 2010 and I did not like how the installation was configured, so we uninstalled everything and removed the SSRS server from the SharePoint farm and uninstalled all the SQL bits (SSRS was deployed to web tier in
sharepoint mode).
I've since added a new application server to host the SSRS SharePoint Mode and Installed the reporting services add-in on the WFE. For reference, I have 1 WFE and 2 App Servers. the WFE has the Reporting Service Add-in and both App Servers have
the SharePoint mode of SSRS installed as described here: https://msdn.microsoft.com/en-us/library/hh479774(v=sql.110).aspx
I've also installed the Service Application and all seems to work well up until I make an attempt to create a report or data source on the WFE.
It looks like somewhere, the WFE is still looking to connect to the original SSRS machine we installed. I've gone through registry, config files and the SharePoint config database to see if I can see where the reference value is. Still can't
find it anywhere. None of the Reporting commandlets are helping.
Technically what is occurring;
Add Reporting service content types and create a New Reporting Data Source through UI
ULS Logs go after the url: /_layouts/ReportServer/NewSharedDataSource.rsds
Exception occurs after some time because it times out trying to connect to wrong host. Exception below:
Exception encountered for SOAP method GetSystemProperties: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <WRONG HOST IP>:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) -
-- End of inner exception stack trace ---
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SetConnectionProtocol()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)
No powershell commands or any of the settings in the service application allow me to set this. Any help would be appreciated.
20 Bay Windows Home Server (Not Vail!)
http://piroozjavan.blogspot.com/

Issue an iisreset on the WFE, and validate that SSRS Service is running on the App servers.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

"Unable to connect to the remote server" error message (ID 6102) in event view after installing MOSS 2007

Hi brothers,
After installed the Moss 2007(basic) , I find some error in event view. The event ID is "6102". More detail information is shown below.
Event Type:        Error
Event Source:    Office SharePoint Server
Event Category:                Launcher Service Event ID:              6102Date:                     11/27/2007Time:                     8:22:17 AMUser:                     N/AComputer:          MOSS-001Description:LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Please help me, thanks.

Hi,
i think this has to do with the "Document Conversions Load Balancer Service".
If you don't need the service than try to stop it:
Start Central Administration > Operations > Services and stop the service.
or
If you need it the service, try this:
Start Central Administration > Operations > Service Account
Change the service account to "Document Conversions Load Balancer Service" And Select a "Network Services" Click Save
Hope this helps!
Cheers,
Daniel Bugday
Web:
SharePoint Forum
Blog:
Daniel Bugday's SharePoint Blog

Possible workaround for: Launch Debugger Error "Unable to connect to the RDS server"

I do not yet have a reproducible case for this. *Sometimes* ColdFusion Builder throws the "Unable to connect to the RDS server" error, when attempting to start a debug session against a remote server. However, "RDS Dataview" and "RDS Fileview" views correctly list the servers and their related data/file, and testing RDS connection result is "Test connection was successful". The workaround is:
1. Login to the ColdFusion Administrator
2. Navigate to "Debugger Settings" page (beneath "Debugging & Logging")
3. Click on "Stop Debugger Server" -or- "Restart Debugger Server"
4. Restart ColdFusion Application Server
Notes:
a) Step #3 must be done via ColdFusion Administrator, not via ColdFusion Admin API (stopLineDebugger()|restartLineDebugger())
b) Step #4 can be done via ColdFusion Administrator -or- ColdFusion Builder
c) Note that there is a CF9 Release Note for Bug #78488: "When a server having "Windows service option" ENABLED is added as a remote server, then Start-Stop-Restart operation cannot be done on it." However, I've found that "Restarting" a remote server, that is running as a Windows service, is possible in ColdFusion Builder (at least this is so on standalone developer edition). Like Bug #78488 says, I am unable to "Stop|Start" a remote server that is running as a Windows service. I'm just mentioning all of this, due to my suggestion in "b", that CF can also be restarted via ColdFusion Builder.
It is interesting that attempts to stop|restart the debugger server, via CF Admin API, do not resolve the issue. So, it seems that the "Stop Debugger Server" and "Restart Debugger Server" buttons, in CF Admin, are doing more than calling the corresponding CF Admin API methods.
Attached is an image of the error.
Just posting all of this as an FYI, in case it helps anyone.
Thanks!,
-Aaron Neff
(OH.. I'm unable to attach images at this time *DOH!* ..well, I'll try to remember to update this post w/ the image, once I see that attachments are allowed.)
I'll try to describe the error message window:
- It is 494x452 pixels
- Title of the window is "Error occurred while launching the Debugger"
- Body content of the window is as follows:
Unable to connect to the RDS server 'ServerNameHere'
Ensure that the server is currently running and that line debugging and RDS are enabled. You may also need to check your RDS connection settings in Eclipse to ensure that they are correct.
Error Message:
-1:Error connecting to JVM for debugging at localhost:5005. Could not attach to the VM at port 5005. You must specify this debugger port in the JVM settings of your application server, for example: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005. You will also need to make sure that another debugger is not currently connected to the CF JVM at the same port (5005).
Root cause ->
Connect refused: connect

hi,
I have been facing the same problems while connecting to Oracle Web Conferencing and is getting error message :Unable to connect to the server. The Web COnferencing Console will now close. Please try again later. If the problem persist, contact your system administrator.
Diagnostic report shows failed on the connectivity part
Connectivity
mx-direct Failed
0:00:00.719 Connecting to web331.oracle.com:1025
0:00:00.922 Name resolved to 148.87.108.234
0:00:21.906 connect() failed (0x8007274C)
0:00:21.906 Connection failed (0x8007274C)
Pl help me to fix the problem.
Regards
Gobind Ahuja

I have windows 7 and Itunes 10. I the the error of Unable to connect to the CDDB server when I try to get tune names

I have windows 7 and Itunes 10. I the the error of Unable to connect to the CDDB server when I try to get tune names. I can still connect to iTunes store and I can still summit track names to the CDDB server. I just cant recive the names from the CD's. I read this problem on the community and I've checked that the proxy server from Lan is unchecked. I use a verizon wireless card for my internet if that matters.

Perhaps try the iTunes Store loads partially or returns "Error 306" or "Error 10054" section in the Specific Conditions and Alert Messages: (Mac OS X / Windows) section of the following document:
iTunes: Advanced iTunes Store troubleshooting

Intermittent proxy error "There is a problem with the proxy server's security certificate. Outlook is unable to connect to the proxy server "

Hi all,
From time to time (at least once a day), the following message pops up on the user's screen:
"There is a problem with the proxy server's security certificate. Outlook is unable to connect to the proxy server . Error Code 80000000)."
If we click "OK" it goes away and everything continues to work although sometimes Outlook disconnects. It is quite annoying...
Any ideas?
Thank you in advance

Hi,
For the security alert issue, I'd like to recommend you check the name in the alert windows, and confirm if the name is in your certificate.
Additionally, to narrow down the cause, when the Outlook client cannot connect again, I recommand you firstly check the connectivity by using Test E-mail AutoConfiguration. For more information, you can refe to the following article:
http://social.technet.microsoft.com/Forums/en-US/54bc6b17-9b60-46a4-9dad-584836d15a02/troubleshooting-and-introduction-for-exchange-20072010-autodiscover-details-about-test-email?forum=exchangesvrgeneral
Thanks,
Angela Shi
TechNet Community Support

AzCopy worked, suddenly stopped working, unable to connect to the remote server

AzCopy was working fine, I was transferring about 670 files to my Azure Files storage account on "https://blah.file.core.windows.net/myshare" (that's not the real account), then it stopped after about 400 files.
Now it continually gives the error "Error parsing destination location
https://blah.file.core.windows.net/myshare: Unable to connect to the remote server."
However it works from a different computer with a completely different IP address in another part of the country.
I am 100% sure my azcopy command is correct, because it worked for about 400 files then stopped, and the exact same command no longer works. I have tried it with both the primary and secondary keys. I've uninstalled and reinstalled azcopy 4.1
and that doesn't help.
Is Azure blocking IPs somehow? What could be wrong?

Hi,
I am glad to hear that you have solved your issue, thanks for posting, if you have any difficulty in future, we welcome you to post in forums again.
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

The WSUS administration console was unable to connect to the WSUS Server via the remote API. (Server 2k8)

I have installed a new server for WSUS on Server 2k8, This is a stand alone server on Internet No client system is connected on this server as I have to copy these updates to my LAN which never connects to internet. (Previously I was using server 2k3. for
online & server 2008 on my LAN , now I have changed the server for Online)
Wsus has finished the synchronization & downloaded updates of around 67GB & its downloading more updates. The server shows me some updates are waiting to approved. but when I click the link for those updates I get following error message.
error code is as follows -
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.WebException -- The operation has timed out
Source
System.Web.Services
Stack Trace:
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()
I Have tried desabling the firewall,disabling the antivirus protection. Tried by changing the default rule Please Help.

Hi Sagar,
First, please check if the RAM is exhausted. When there is not enough RAM, this issue may occurs.
Please try to run iisreset on the WSUS server, then try to reconnect.
Also, please try to run the server cleanup wizard to remove the unused update.
Best Regards.
Steven Lee 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 Support, contact [email protected]

Outlook is unable to connect to the proxy server.(Error Code 10)

Hi,
I had problems with RPC proxy, I was trying to setup cutover migration.
So I read somewhere that i need to change the certprincipalname with Set-Outlookprovider.
But after this change my outlook was not working anymore
The settings before the change were:
Name Server CertPrincipalName TTL
EXCH
1
EXPR
1
WEB
1
So I set this back to the original (above) but this didn't helped...
Outlook 2013 and Exchange 2013
There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site mail.abc-company.com.
Outlook is unable to connect to the proxy server.(Error Code 10)

Hi,
Please make sure the mail.abc-company.com is included in your Exchange certificate which has been assigned with IIS service.
If possible, please run the following command for double check:
Get-ExchangeCertificate | FL
For Autodiscover service, please run
Test E-mail AutoConfiguration to check if the connection is successful in Log tab and confirm the other services URL can use proper namespace in Results tab for request access.
If the Autodiscover service fails, please create a SRV record with mail.abc-company.com for Autodiscover service to have a try:
http://support2.microsoft.com/kb/940881/en-us
Regards,
Winnie Liang
TechNet Community Support

Outlook is unable to connect to the proxy server. (Error code 0)

Hello,
I have just commenced a Exchange 2007 SP3 to Exchange 2013 SP1 migration following the following guide: http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
As per the above guide, my 2007 environment is now known as legacy.company.com and my 2013, webmail.company.com.
I'm using the same certificate on both boxes and it has the names autodiscover.company.com, webmail.company.com and legacy.company.com. All that seems to be working fine.
OWA is functioning perfectly, hitting https://webmail.company.com will pass the user off to https://legacy.company.com if the mailbox is on 2007. Alongside this, Outlook also has no issues connecting to 2007 mailboxes with the client proxy settings
being reconfigured to https://legacy.company.com automatically.
My problem comes when a mailbox is migrated to 2013. OWA functions fine and presents the mailbox but Outlook is unable to connect, presenting the error:
There is a problem with the proxy server's security certificate.
The name on the security certificate is invalid or does not match the name of the target site webmail.company.com.
Outlook is unable to connect to the proxy server. (Error Code 0)
If I modify the Outlook client's settings and disable "Only connect to proxy servers that have this principal name in their certificate: msstd:webmail.company.com", Outlook connects and functions fine.
I'm at a loss and have tried everything I can think and find on google. Any suggestions would be greatly appreciated.

Hi,
Please refer to the following article :
http://support.microsoft.com/kb/923575
Cause:
This issue may occur if one or more of the following conditions are true:
The connection to the server requires a certification authority (CA).
You have not trusted the certification authority at the root.
The certificate may be invalid or revoked.
The certificate does not match the name of the site.
A third-party add-in is preventing access.
Solution:
To examine the certificate, follow these steps:
In Microsoft Internet Explorer, connect to the RPC server or to the secure server. For example, type
https://www.<var>server_name</var>.com/rpc in the Address bar of the Web browser, and then press ENTER.
Note The <var>server_name</var> placeholder references the RPC server name or the secure server name.
Double-click the padlock icon that is located in the lower-right corner of the Web browser.
Click the Details tab.
Note the information in the following fields:
Valid to
The Valid to field indicates the date until which the certificate is valid.
Subject
The data in the Subject field should match the site name.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Outlook is unable to connect to the proxy server.(Error Code 10) when users opened Outlook 2010

Hi All
Exchange Server - 2013 CU2 (Windows 2012 Standard)
AD Server - 2003 R2 SP2
exchange-svr01.domain.com - internal name
mail.company.net - external name
When users opened Outlook 2010, they will encountered
"There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site exchange-svr01.domain.com.
Outlook is unable to connect to the proxy server.(Error Code 10)"
I also used the Microsoft Remote Connectivity Analyzer to test RPC/HTTP connectivity.
The RPC/HTTP test completed successfully.
    Validating the certificate name.
    Certificate name validation failed.
     Host name company.net doesn't match any name found on the server certificate CN=AMAZONA-U59HG9G.
Testing SSL mutual authentication with the RPC proxy server.
    The test passed with some warnings encountered.
The certificate common name company.net doesn't match the mutual authentication string provided mail.company.net; however, a match was found in the subject alternative name extension.
please help.

Hi PS CL
[PS] C:\Windows\system32>Get-OutlookAnywhere
RunspaceId                         : c457e8aa-a0f3-4a0f-aa02-9eff24d02821
ServerName                         : exchange-svr01
SSLOffloading                      : True
ExternalHostname                   : mail.company.net
InternalHostname                   : exchange-svr01.domain.com
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://exchange-svr01.domain.COM/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 712.22)
Server                             : exchange-svr01
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web
                                     Site),CN=HTTP,CN=Protocols,CN=exchange-svr01,CN=Servers,CN=Exchange
Administrative
                                     Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=domain,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=domain,DC=COM
Identity                           : exchange-svr01\Rpc (Default Web Site)
Guid                               : 33c3cb74-e490-487d-844c-4072334089a1
ObjectCategory                     : domain.COM/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 8/17/2013 10:14:55 AM
WhenCreated                        : 6/25/2013 1:47:50 PM
WhenChangedUTC                     : 8/17/2013 2:14:55 AM
WhenCreatedUTC                     : 6/25/2013 5:47:50 AM
OrganizationId                     :
OriginatingServer                  : ADserver.domain.COM
IsValid                            : True
ObjectState                        : Changed

Web Service Error : Unable to connect to the remote server

Hi,
I encountered below errors while I run the web service in ERP 2006 system :
Unable to connect to the remote server,
No connection could be made because the traget machine actively refused at xxx.xxx.xxx.xxx:443
Pls kindly advise.
Thanks.
Edward Tso

Hi,
Do you have proxy server , check property added t.o the java proxyparameter .
Also check the log , any fire wall restricting the connection.
Its better, you put error log you get.
Regards
Nagaraju

Server cleanup wizard problem - unable to connect to the WSUS Server Database.

I'm trying to run server cleanup wizard.. it starts to run and then after a while it gives me this error:
The WSUS administration console was unable to connect to the WSUS Server Database.
Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.
System.Data.SqlClient.SqlException -- Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Source
.Net SqlClient Data Provider
Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.InitializeDerivedProperties()
   at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.get_NewUpdatesCount()
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetSyncInfoRow(WsusSynchronizationInfo syncInfo)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetListRows()
Thanks

Some questions:
Are there any other databases running on this Std Edition SQL service?
[a] Yes there are, we have Kaspersky enterprise DB, Report Server DB and local application DB.
Are there any other services running on this WSUS Server?
[b] Yes there are, we have Active Directory, Kaspersky enterprise, SQL Server 2005, and WSUS all on the same server.
How many days since your WSUS server was first installed?
[c] It's been about a year now.
What is the physical size of the SUSDB.mdf file?
[d] 9,666,752 KB
What is the hardware configuration of this machine, including disk drives?
[e] Intel Xeon 1.86, 2GB Ram, HD C: 39GB - E: 25.2, running Windows Server 2003 R2 SP2.
How many client systems are you servicing from this WSUS Server?
[f] Around 40.
What products/classifications are you synchronizing.
[g] Windows XP-vista, Windows Server 2003, Office 2003-2007, SQL Server 2005.
Okay, for starters, you have an underpowered/overextended machine running Active Directory, ASP.NET, and a database server, all on a sub 2GHz CPU with 2GB RAM, and not enough disk spindles. The machine has had WSUS running for about a year and is 9GB in size.
There's no doubt in my mind that some of your performance issues are directly related to disk and database fragmentation.
There's also no doubt that some of your performance issues are directly related to memory starvation.
I'd suggest the following long-term fixes:
1. Get a second machine. Make it a dedicated database server. Provision it accordingly to support servicing multiple database applications.
2. Lacking #1, this machine needs more memory. It also needs more disk spindles. At a minimum the databases being serviced should be on a dedicated physical drive; ideally there would be two dedicated drives allocated for supporting database services. The
For the short-term fixes, do this:
1. During after-hours time, if you don't already have one, build a temporary machine that can act as a DC/GC, while you take this machine temporarily offline.
1. Shutdown the Update Services service, SQL Server database engine, and any other services dependent on the SQL Server database engine (Kapersky, and other reporting applications). Disconnect from the network to temporarly eliminate DC traffic. (You could also shutdown the AD services, but disconnecting the network cable is ever-so-much easier.) Defragment ALL drives.
2. Restart ONLY the SQL Server service. Obtain this SQL script to Reindex the WSUS Databases.
3. Restart ONLY the Update Services service. Attempt the Server Cleanup Wizard again. Run it in two passes. Pass 1 performing everything except remove unused updates. Pass 2 running only remove unused updates.
4. After completion of the Server Cleanup Wizard, reconnect the machine to the network and resume all other services.
5. If you're able to complete #3, secure the services of a well-qualified DBA to determine if there are any misconfigurations in your SQL Server setup that would account for why your WSUS database is 9GB in size -- such as improperly configured autogrowth parameters. Based on the products you're updating and only forty clients, 9GB is about 3x the maximum size I would expect to see in a WSUS database. It's possible this is simply caused by excess unused updates, it's possible it's caused by fragmentation, it's probable it was caused by unnecessary autogrowth of the database due to insufficient update maintenance. You'll want a DBA to assist you in shrinking that database after you successfully run the Database Maintenance and Server Cleanup Wizard.
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

Unable to connect to the report server

I have a problem with run_report_object to call a report within a form. I am using 9ias Rel 2 and report server on the same machine. The test.rdf report can be executed using the URL in the browser.
I get the "Unable to connect to the report server" when I use the run_report_object in a form. Is it a configuration problem or is the code incorrrect?
My code is as follows:
Declare
repid report_object;
report_job_id VARCHAR2(200);
PL_ID PARAMLIST;
rep_status varchar2(100);
Begin
repid := FIND_REPORT_OBJECT('OP201P');
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_EXECUTION_MODE, BATCH);
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_COMM_MODE, SYNCHRONOUS);
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_DESTYPE, CACHE);
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_DESFORMAT,'pdf');
SET_REPORT_OBJECT_PROPERTY(repid, REPORT_SERVER,'repsrv');
PL_ID := CREATE_PARAMETER_LIST('TEMP');
ADD_PARAMETER(pl_id, 'p_ref1', TEXT_PARAMETER,:toolbar.ref1 );
ADD_PARAMETER(pl_id, 'p_ref2', TEXT_PARAMETER,:toolbar.ref2 );
ADD_PARAMETER(pl_id, 'p_sort', TEXT_PARAMETER,:toolbar.p_sort );
report_job_id := RUN_REPORT_OBJECT(repid, pl_id);
rep_status := REPORT_OBJECT_STATUS(report_job_id);
WHILE rep_status in ('RUNNING','OPENING_REPORT','ENQUEUED')LOOP
rep_status := REPORT_OBJECT_STATUS(report_job_id);
END LOOP;
IF rep_status = 'FINISHED' THEN
Web.show_document('http://portal.domain_name.com:7778/getjobid='||
substr(report_job_id,9) || '?server=repsrv', '_blank');
ELSE
message('Report failed with error message '|| rep_status);
END IF;
end;
For the show_document, I have tried both ' .. getjobid='|| substr(report_job_id,9)' and
' .. getjobid'|| substr(report_job_id,9)' .
Any help would be greatly appreciated.
Thank You.
Rgds
Edwin

Hi ,
Did you check if TCP/IP is enabled for the SQL Server service.
If Disable you may need to enable it.
To resolve this error, you can either modify the connection string to use the server name or you can enable TCP/IP for the service. Follow these steps to enable TCP/IP:
1) Start SQL Server Configuration Manager.
2) Expand SQL Server Network Configuration.
3) Select Protocols for MSSQLSERVER.
4) Right-click TCP/IP, and select Enable.
5) Select SQL Server Services.
6) Right-click SQL Server (MSSQLSERVER), and select Restart.
Also Check the below link.
Hi ,
Did you check if TCP/IP is enabled for the SQL Server service.
If Disable you may need to enable it.
To resolve this error, you can either modify the connection string to use the server name or you can enable TCP/IP for the service. Follow these steps to enable TCP/IP:
1) Start SQL Server Configuration Manager.
2) Expand SQL Server Network Configuration.
3) Select Protocols for MSSQLSERVER.
4) Right-click TCP/IP, and select Enable.
5) Select SQL Server Services.
6) Right-click SQL Server (MSSQLSERVER), and select Restart.
Also Check the below link if doesn't work from above.
http://msdn.microsoft.com/en-us/library/ms365170.aspx
Regards, PS

Unable to connect to the Exchange server using HTTP/HTTPS protocol.

hi,
i try to connect microsoft exchange server, but it give me
error
Unable to connect to the Exchange server using HTTP/HTTPS
protocol.
my code is pasted below............

<cfparam name="user1" default="uHRH">
<cfparam name="user2" default="uHRH">
<cfparam name="password" default="uHRH">
<cfparam name="exchangeServerIP" default="192.168.0.1">
<cftry>

<cfexchangeConnection
action="open"
username ="#user1#"
password="#password#"
server="#exchangeServerIP#"

connection="conn1">
<cfoutput>Connection to exchange server
"#exchangeServerIP#" established</cfoutput>

<CFExchangeConnection
action="close"
connection="conn1">
<cfoutput>Connection to exchange server
"#exchangeServerIP#" terminated</cfoutput>

<cfcatch type="any">
<cfoutput>#cfcatch.message#</cfoutput>
</cfcatch>
</cftry>
if any one know how to solve this error?

Hi,
The "<cfexchangeConnection>" tag supports both "HTTP"
and "HTTPS" connection.. So Please make sure the username has the
"Outlook Web Access".
Also try removing the 
comment which you placed inside the "<cfexchangeConnection>"
tag.

Unable to connect to the Livecycle Server in CM (Non Turnkey Install)

Similar Messages

Maybe you are looking for