Windows 2008 Terminal Server issue after swapping modem/router

Hi, I have a problem I just can't crack.
Windows 2008 Terminal Server, all patched and up to date. The IP Address is 192.168.1.11 (on a teamed intel controller). Terminal services enabled and working ok.
TP-Link Modem 192.168.1.1, RDP Port forwarded ok.
Set the Windows gateway to 192.168.1.1 and external access to RDP is not a problem.
We had some modem speed issues, so we got a much faster connection, but it can't be used for incoming RDP, so left the TP-Link in place. So added a 3G modem at 192.168.1.5 and set that as the gateway.
External RDP access still works perfectly, and now users have much faster internet.
The TP-Link is giving some reliability issues, so I swapped it over for another modem, a Billion modem. Same 192.168.1.1 IP address, same port forwarding. External RDP access is no longer possible.
Swap back to the TP-Link and everything is fine. Test the modem on another site, everything works as expected.
If I set the gateway on the terminal server to 192.168.1.1 with the Billion attached then external RDP access is no problem. If I set it to 192.168.1.5 then it stops working again.
I tried with a new TP-Link modem of the same model with exactly the same settings and this also had the same problem. External RDP access will only work the existing TP-Link modem, which is a problem as the modem appears to be faulty.
It's almost like it hasn't worked out that it's a new network, and when Windows does that it seems to lock down RDP. That is only my assumption from experience of moving computers to new networks and RDP won't work until windows prompts you with the new
network screen to select home, office or public.
Has anyone experienced anything like this before or can shed some light on the problem?
Thanks.

Hi,
How is the issue going now? Is there any update?
Thanks.
Jeremy Wu
TechNet Community Support

Similar Messages

Acrobat 9 Reader with Windows 2008 Terminal Server

I am setting up a Windows 2008 Terminal Server and i need to have the Adobe Acrobat Reader installed. I downloaded and installed the Vista version and it worked from the console but when i try to access it via a terminal server session the application just crashes. If i try and run it as administrator in the same terminal server session it launches fine.
Any suggestions????
Jason
p.s The associated event log error is:
Log Name:      Application
Source:        Application Error
Date:          7/31/2008 1:17:57 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Comet.invera.com
Description:
Faulting application AcroRd32.exe, version 9.0.0.332, time stamp 0x4850f0a3, faulting module Annots.api, version 9.0.0.332, time stamp 0x4850e57f, exception code 0xc0000005, fault offset 0x001bd9e0, process id 0x1458, application start time 0x01c8f3316002e3b7.
Event Xml:
    1000
    2
    100
    0x80000000000000
    3663
    Application
    Comet.invera.com
    AcroRd32.exe
    9.0.0.332
    4850f0a3
    Annots.api
    9.0.0.332
    4850e57f
    c0000005
    001bd9e0
    1458
    01c8f3316002e3b7

Jason...
Make Certain that you Had the Server In "TS-Install" Mode When you Installed Acrobat. It Is In your Control Panel. I Have Pasted the MS Help File Below.
Install Programs on a Terminal Server
You should install the Terminal Server role service on the computer before you install any programs that you want to make available to users. If you install the Terminal Server role service on a computer that already has programs installed, some of the existing programs may not work correctly in a multiple user environment. Uninstalling and then reinstalling the affected programs may resolve these issues.
To ensure that an application is installed correctly to work in a multiple user environment, you must put the terminal server into a special installation mode before you install the application on the terminal server. This special installation mode ensures that the correct registry entries and .ini files that are needed to support running the application in a multiple user environment are created during the installation process.
You can put a terminal server into this special installation mode by using either of the following:
Install Application on Terminal Server tool under Programs in Control Panel. This tool will run a wizard to help install the application.
Change user /install command at a command prompt. You will have to start the installation of the application manually.
After the application is installed, you must put the terminal server into execution mode before remote users begin using the application. The Install Application on Terminal Server tool will automatically put the terminal server into execution mode when it is finished running. To put the terminal server into execution mode from a command prompt, use the change user /execute command.
Additional considerations
Some programs may require minor setup modifications to run correctly on a terminal server.
If you have programs that are related to each other or have dependencies on each other, you should install the programs on the same terminal server. For example, you should install Microsoft Office as a suite on the same terminal server instead of installing individual Office programs on separate terminal servers.
You should consider installing individual programs on separate terminal servers in the following circumstances:
The program has compatibility issues that may affect other programs.
A single program and the number of associated users may fill server capacity.
For more information about the change user command-line tool, see the Terminal Services Command Reference (http://go.microsoft.com/fwlink/?LinkId=89674).
For more information about deploying programs on a terminal server, see the Terminal Server page on the Windows Server 2008 TechCenter (http://go.microsoft.com/fwlink/?LinkId=79608).

Add Windows 2008 Terminal Server to RWW/RWA

I would like to add our Windows 2008 Terminal Server (not R2) to RWW in Windows 2012R2 Essentials. The connect computer wizard did not work on the Windows 2008 server, returning Win32 error.
How do I add the 2008 TS to the devices listing in RWW without using the connector wizard (as it does not work). The Windows 2008 server has been join to the same domain manually.

You cant add it as a tile device in the way you could in SBS 2011 Standard.
You can create an RDP file, and save that so it is accessible via the RWA then add a link to the RWA to that file.
You may need to tweak IIS to allow .rdp files.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Windows 2008 Terminal Server, Acrobat 7, 9

Hello,
I have Acrobat 7 installed on a Windows 2008 terminal server. Anyone with a terminal session that has Acrobat 7 installed on the local workstation is able to create Acrobat documents. Why is it that anyone with a terminal session that has Acrobat 9 installed on the workstation is not able to create Acrobat documents?
Thank you,
techctzn808

I replied to your other message
http://forums.adobe.com/thread/536492?tstart=0

Windows 2008 Terminal Server "user must change password at next logon" problem with Windows 7 client.

Hi,
I have a fully patched Windows 2008 SP2 Terminal Server and a fully patched Windows 7 client.
I have logged into the Windows 2008 SP2 Terminal Server server with a test account via RDC before.
When I try to log in via RDC to the 2008 TS with a test account which has been marked with the setting "User must change password at next logon" I get the RDC message "You must change your password before logging on the first time. For assistance, contact your system administrator or technical support." I need to force the user to change their password once it has been issued, any ideas on how this can be done?
Thanks,
Dan

This does not resolve my issue all the way. I'm having the same problem; When i'm "deploying" users, i always want the users to set their own passwords. Ok, so I then set the auth mode to "RDP Security layer". It seemed to work fine, and it does for that
special purpose.
Just like Daniel, my clients are connecting to our terminal server from several/different "customer-domains" So, they can't logon locally(on their local computer) and change their password, it has to be done THROUGH the terminal server.
But if I turn on RDP Security Layer, users can't use remoteapp through tsgw they only get: "Your Remote Desktop Connection Failed because the remote computer cannot be authenticated" Any ideas?
Also, our terminal servers is round robin based in a farm. So users connect to: tsfarm.domain.com(yes, public a-record which resolves to two internal adresses) This is because, we're using a wilcard *.domain.com as SSL certificate.
But, when i'm using this, our clients sometimes get double auth when they login. I only get the double auth when tsfarm.domain.com resolves to server A, but the session broker wants the user to be on server B.(load balancing)
This does not occur when SSL is enforced, any ideas?

Cannot install Office 2010 on Windows Server 2008 terminal server

Hello
I have a Windows 2008 terminal server which has Office 2007 Professional Plus on it. We want to upgrade it to Office 2010 Professional Plus.
Following steps from Technet, I made sure all users were out of the terminal server, then selected "Install Application on Terminal Server", then ran the setup.exe file for Office 2010.
The splash screen comes up for Office 2010 but then disappears and the install does not progress, although the setup.exe is still running in Task Manager. The "install Application on Terminal Server" window is still open, waiting for me to click
Next, Finish or Cancel and nothing else happens.
I also tried putting the server into install mode from command prompt and rebooting the server and re-attempting but no good.
How can I go about troubleshooting this issue?
Many thanks
Luke Dunster

Hi Luke,
Are you using a volume license version of Office 2010 for Remote Desktop Services/Terminal
Services? I may be wrong but I think that only this version of Office 2010 will work on a Terminal
Server. The Retail Version will just not work in this case.
I had similar problem where I tried to upgrade from Office 2007 to Office 2010 on a Terminal Server (Windows
2008) but wasn't successful with the upgrade/installation.
Also take a look at this post:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/e09ee781-82c2-4399-85f4-1b90ae690ccb/office-2010-licensing-for-windows-2008-rdsterminal-services-pkc-ok?forum=winserverTS
Jale01

Redirect Printer is not working in windows 2008 R2 Server( Server Running as AD and Terminal Service(both role in single server))

Dear Team
i need solution from Microsoft for the issue;
My infrastructure
- Windows Server 2008 R2 (Role - AD and Terminal Service)- Updated
- Client Machine running with windows 7 pro (Updated)
- Client Using RDP Client to connect Windows 2008 Terminal Session
- All are working fine, but Redirect Printing is not working (Through Windows 7 Pro) ... (HP Laser Jet 1020 plus - attached in Client PC)
- it is working fine from Windows XP
- i was done All terminal setting in both end, also try RDP Login with Administrator User, but issue is not resolve;
What Microsoft can say about the issue;
Thanks & Regards,
VIMAL PRAJAPATI | 09824111686

Have you checked the Print Service log in event viewer?
Here's How.
I have the Microsoft XPS driver on my clients, so I use that fact to my advantage below.
Click Start Button/Administrative Tools/Remote Desktop Services/Remote Desktop Services Manager on the RDSH server
Click the Sessions tab. PC’s are listed Under Client Name by their computer name. Take Note of the corresponding
ID. We will use this to locate the Printer information in the Event Log.
In the Event Log open Application and Services Logs/Microsoft/Windows/Print Service/Admin/ and Find the Event ID 823 entry that has the corresponding ID from the sessions tab you previously noted.
This Event Log Entry is created at Logon and you can only get the session ID when they are logged in.
This tells you what client printer was mapped for the client. The name that appears is the name of the Printer that was set on the client when the printer was installed.
See if you see any errors here.
If you see Event Id 823 with the following message “The default printer was changed to Microsoft XPS Document Writer,winspool,Ne00:. See the event user data for context information.” Twice in a row with no other messages in between, and the first occurs
at the time the user logged in, then their printer was not properly redirected.
You see the Microsoft XPS driver mapped for each session prior to Easy Print redirecting the client machine’s Default Printer.
Since your printer is the HP 1020 I would bet the driver on the client does not work with Easyprint. I would try the the HP Universal Print Driver or the driver for a printer that is very close, like the HP 1018.
Thanks,
Jeremy

Windows 2008 R2 Client computer backup files (*.dat) can't get restored after re-imaging the Windows 2008 R2 server

I have a Windows server 2008 R2 and I'm using backup feature to backup all computers in the network on it. Recently I ran into an issue and had to re-image my Windows 2008 R2 server and had to restore 2 of my client computers but now I can't restore
files from my client computer backups because they are not listed under Backups & Devices anymore however all backup files are still available on my Backup drive. How can I retrieve files from these backup files?

Anyone out there to help me with this issue?

Issues in running flash player activeX on 64 bit windows 2008 R2 server

When the activeX acts up, users can not type anything into search boxes or use the keyboards in online game sites. From time to time, we have to re-install flash player again.
We noticed that the FlashUtil64 activeX dll is somehow saved in c:\windows\system32\Macromed\Flash folder while the FlashUtil32 activeX dll is in c:\windows\syswow64\Macromed\Flash folder, is this normal? And when running 32 IE, the flashutil64 shown in the windows running process.
We installed flash player with 32 bit IE 10 on a 64 bit windows 2008 R2 server.
Thanks.

It seems you have used 32bit installers on 64bit machine. Please refer -
http://anuj-dwivedi.blogspot.com/2010/10/installing-oracle-soa-and-bpm-111130.html
Regards,
Anuj

Wyse Thin client not connecting to Windows 2008 R2 server

Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.

We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits

Unable to login to Report Service on Windows 2008 R2 server

I have reporting services installed on a Windows 2008 R2 server, When I make and RDP connection to the server and go to http://servername/Reports everything works fine. When I try to connect from another client to the web service, it asks for username and
password. it fails 3 times and the shows a blank page.
When I see the Event Viewer in the server (Windows Logs --> Security, I can see an Audit Failure:
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          9/4/2014 11:46:25 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      MI-SWACO-DB.houston.livequest.net
Description:
An account failed to log on.
Subject:
   Security ID:       NULL SID
   Account Name:       -
   Account Domain:       -
   Logon ID:       0x0
Logon Type:           3
Account For Which Logon Failed:
   Security ID:       NULL SID
   Account Name:       Administrator
   Account Domain:       HOUSTONLQ
Failure Information:
   Failure Reason:       An Error occured during Logon.
   Status:           0xc000035b
   Sub Status:       0x0
Process Information:
   Caller Process ID:   0x0
   Caller Process Name:   -
Network Information:
   Workstation Name:   MI-SWACO3
   Source Network Address:   -
   Source Port:       -
Detailed Authentication Information:
   Logon Process:
   Authentication Package:   NTLM
   Transited Services:   -
   Package Name (NTLM only):   -
   Key Length:       0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
   - Transited services indicate which intermediate services have participated in this logon request.
   - Package name indicates which sub-protocol was used among the NTLM protocols.
   - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-04T16:46:25.247229500Z" />
    <EventRecordID>8917</EventRecordID>
    <Correlation />
    <Execution ProcessID="504" ThreadID="1344" />
    <Channel>Security</Channel>
    <Computer>MI-SWACO-DB.houston.livequest.net</Computer>
    <Security />
</System>
<EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">Administrator</Data>
    <Data Name="TargetDomainName">HOUSTONLQ</Data>
    <Data Name="Status">0xc000035b</Data>
    <Data Name="FailureReason">%%2304</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">
    </Data>
    <Data Name="AuthenticationPackageName">NTLM</Data>
    <Data Name="WorkstationName">MI-SWACO3</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
</EventData>
</Event>
The firewall is OFF in both client and server.
I saw a similar question and the answer is related to firewall which is not may case.

Hi Mario,
According to your description, when you try to access the Report Manager in another client, a login dialog prompt. After typing a valid username and password 3 times, a blank page displays.
Generally, the issue is always caused by the Report Server is configured to use Kerberos authentication, while the Service Principal Name(SPN) is not configured correctly. To fix this issue, please refer to the following methods:
Register an SPN for the Report Server service under the domain user account.
Change the service account to run under a built-in account such as Network Service.
Remove RSWindowsNegotiate and ensure RSWindowsNTLM is specified in the rsreportserver.config file.
Besides, the issue can also be caused by the Internet Explorer (IE) didn't pass the user's credential to the Report Server automatically or the IE is not Windows Integrated enabled. For more detail steps about how to address this issue, please refer to the
following steps:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/184c4f6c-b292-4f9a-beca-80b70f4392fe/report-manager-prompts-3-or-4-times-for-usernamepassword-before-letting-users-in?forum=sqlreportingservices
Reference:
Resolving Kerberos Authentication Errors When Connecting to a Report Server
Solving the Reporting Services Login issue in the February CTP of SQL Server 2008
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Moving SAP Content Server/MaxDB 7.6 to a Windows 2008 R2 Server

Hi All.
We are in the process of upgrading our server where the SAP content server is located. We are going from SAP CS 6.30/MaxDB 7.6 to a Windows 2008 R2 server where we want to install SAP CS 6.40/MaxDB 7.8. I have been following the latest manual from SAP for upgrading to MaxDb 7.8 (2010-10-05) from MaxDb 7.6 using the in-place method.
To date we have installed MaxDB 7.6 on the server. We restored our latest backup and performed the index checks as spelled out in the manual. I have the database in ADMIN mode and went to run the MaxDb 7.8 install for the 64 bit window version. THe install GUI comes up, but the Update selection is grayed out. This tells me that the install program can not detect our existing database. I did make sure I was running the install as Admim so I do not think that is the issue.
This is the second time I have tried this upgrade. The first time I did a comand line upgrade by runing the .bat file DBUPDATE.bat. We have a 110 Gbyte database and this upgrade ran in about 15 minutes, and of course when I went to openthe database it was toast. Do not want to make the same mistake again.
One other point, since we did a restore of the database, then the index check, we did not run a backup as the manual suggested as we felt it was not necessary. Does the system require a backup before upgrade and that is why it does not see the database?
Any assistance will be greatly appreciated.

I beleive we have resolved the issue with upgrading the database, but now we are having a problem with Datbase Studio 7.8. Before the upgrade we used Data Manager 7.6. After the upgrade we installed Database Studio 7.8 and when we go to start it up, we are getting the Problems opening perspective 'com.sap.sdb.tools.ut.perspectives.mainPerspective'. I followed the instruction in another post Problems opening perspective in Database Studio, but we still are getting the error.
Can anybody offer any assistance as we are getting close to the weekend when we want to do the cutover and we are not even done with our first pass at upgrading the SAP content server.
Thanks
John

INS-20802: Problem installing Grid Infrastructure on Windows 2008 R2 Server

Hello,
I try to install the Grid Infrastructure on a Windows 2008 x64 Server. Everything works fine (the SCAN configuration and Verify) but at the end of the installation process I get the following error message:
[INS-20802]: Grid Infrastructure Configuration not successfull.
The errors that I found in the file oraInstall2012-02-27_11-58-26AM.log inside the INVENTORY\LOGS directory :
INFO: Unable to read C:/app/11.2.0/grid/inventory/ContentsXML/comps.xml. Some inventory information may be lost.
INFO: Install type for "Oracle Database 11g 11.2.0.3.0 " is "ASM".
INFO: Conflict while setting install type of "Required Support Files 11.2.0.3.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.assistants.server 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ntrdbms.oraconfig 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.xdk 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.xdk.server 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.mgw.common 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.install.seeddb 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ctx 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.owb.rsf 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.sysman.console.db 10.1.0.2.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.oci 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.ovm 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.sqlj.sqljruntime 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.rdbms.hsodbc 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.marvel 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.dbdev 11.2.0.3.0.
INFO: OUI-10066:Not all the dependencies for the component Oracle Database 11g 11.2.0.3.0 could be found. Missing component oracle.dbjava.server 11.2.0.3.0.
INFO: Install type for "Cluster Ready Services Files 11.2.0.3.0 " is "Complete".
INFO: Conflict while setting install type of "HAS Common Files 11.2.0.3.0 " to "Complete (Complete)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle Net Listener 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Internet Directory Client 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle JVM 11.2.0.3.0 " is "Typical".
INFO: OUI-10066:Not all the dependencies for the component Oracle JVM 11.2.0.3.0 could be found. Missing component oracle.javavm.companion 11.2.0.3.0.
INFO: Install type for "Oracle Net 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Netca Client 11.2.0.3.0 " is "Typical".
INFO: Install type for "SQL*Plus 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Database Utilities 11.2.0.3.0 " is "Typical".
INFO: OUI-10066:Not all the dependencies for the component Oracle Database Utilities 11.2.0.3.0 could be found. Missing component oracle.omwb 10.1.0.1.0.
INFO: Install type for "Oracle Recovery Manager 11.2.0.3.0 " is "Typical".
INFO: Install type for "PL/SQL 11.2.0.3.0 " is "Typical".
INFO: Install type for "HAS Files for DB 11.2.0.3.0 " is "Typical".
INFO: Install type for "Assistant Common Files 11.2.0.3.0 " is "Typical".
INFO: Conflict while setting install type of "Oracle Help For Java 4.2.9.0.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Buildtools Common Files 11.2.0.3.0 " to "Typical (Typical)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Sun JDK 1.5.0.30.03 " to "Maximum (Complete)". Install type already set to "Maximum (Complete)". Seting it to "Custom (Custom)".
INFO: OUI-10066:Not all the dependencies for the component Assistant Common Files 11.2.0.3.0 could be found. Missing component oracle.bali.kodiak 1.2.1.0.0I.
INFO: Install type for "HAS Common Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle Multimedia 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Multimedia Locator 11.2.0.3.0 " is "Typical".
INFO: Install type for "Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Conflict while setting install type of "Oracle Net Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle Globalization Support 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle Core Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "RDBMS Required Support Files 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle RAC Required Support Files-HAS 11.2.0.3.0 " to "Custom (Custom)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle JDBC/THIN Interfaces 11.2.0.3.0 " is "Typical".
INFO: OUI-10066:Not all the dependencies for the component Oracle JDBC/THIN Interfaces 11.2.0.3.0 could be found. Missing component oracle.dbjava.ucp 11.2.0.3.0.
INFO: Install type for "Oracle Core Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Installation Common Files 11.2.0.3.0 " is "Typical".
INFO: Install type for "Precompiler Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Parser Generator Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Agent Required Support Files 10.2.0.4.3 " is "Custom".
INFO: Install type for "XDK Required Support Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle RAC Required Support Files-HAS 11.2.0.3.0 " is "Custom".
INFO: Install type for "Buildtools Common Files 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle Globalization Support 11.2.0.3.0 " is "Custom".
INFO: Install type for "Oracle Locale Builder 11.2.0.3.0 " is "Custom".
INFO: Conflict while setting install type of "Oracle JFC Extended Windowing Toolkit 4.2.36.0.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle Clusterware RDBMS Files 11.2.0.3.0 " is "Typical".
INFO: Install type for "Cluster Verification Utility Common Files 11.2.0.3.0 " is "Typical".
INFO: Install type for "CFS 11.2.0.3.0 " is "Complete".
INFO: Install type for "Oracle Notification Service (eONS) 11.2.0.3.0 " is "Typical".
INFO: Install type for "Cluster Verification Utility Files 11.2.0.3.0 " is "Complete".
INFO: Install type for "Oracle LDAP administration 11.2.0.3.0 " is "Typical".
INFO: Install type for "Deinstallation Tool 11.2.0.3.0 " is "Complete".
INFO: Conflict while setting install type of "Oracle Database Deconfiguration 11.2.0.3.0 " to "Complete (Complete)". Install type already set to "Typical (Typical)". Seting it to "Custom (Custom)".
INFO: Install type for "Enterprise Manager Common Files 10.2.0.4.3 " is "Complete".
INFO: Install type for "Oracle Notification Service 11.2.0.3.0 " is "Typical".
INFO: Install type for "Oracle Help For Java 4.2.9.0.0 " is "Custom".
INFO: Conflict while setting install type of "Bali Share 1.1.18.0.0 " to "Custom (Custom)". Install type already set to "Maximum (Complete)". Seting it to "Custom (Custom)".
INFO: Conflict while setting install type of "Oracle Ice Browser 5.2.3.6.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
INFO: Install type for "Oracle Ice Browser 5.2.3.6.0 " is "Custom".
INFO: Conflict while setting install type of "Oracle Extended Windowing Toolkit 3.4.47.0.0 " to "Custom (Custom)". Install type already set to "Complete (Complete)". Seting it to "Custom (Custom)".
I have read and implemented all the settings described in DOCs ID 811271.1 , ID 810394.1 and RAC on Windows Step by Step Installation Instructions.
After many attempts with the same error Ii am trying to install in a single node (RAC1). But the error looks the same, my server is clean with no oracle.
Note: For this installation I downloaded and uncompressed the files p10404530_112030_MSWIN-x86-64_1of7.zip, p10404530_112030_MSWIN-x86-64_2of7 and p10404530_112030_MSWIN-x86-64_3of7 of the oracle site.
I do not know what to do for this installation work.
Thanks

My recommendation would be to format the disks and install Linux.
And I say that only half-jokingly. Fail-over with Windows is never as fast or as transparent as with a *NIX O/S.
As to your specific issue ... open an SR with Oracle Support. Hardly anyone uses Windows for Oracle ... even fewer with RAC ... for the reason I gave above.

I dream of running Dreamweaver on a Windows 2003 Terminal Server

I have a "volume" license and attempted to install Dreamweaver CS4 on a Windows 2003 Terminal Server. I get an error message right away indicating that the system does not meet the minimum install requirements, ie XP/Vista.
Adobe volume licensing team verified that it is the correct license for installing on a terminal server, but after one hour of what would a bad nightmare with adobe "no" support (Outsourcing issue, failure to grasp and process the basic error message) I got no where and am having to resort to the forums. I have googled on this and got no where and nothing on the search efforts on this site.
If anyone has an idea of what is going on, bug, wrong install media, please clue me in.
Thanks!

pziecina
Thanks for the information. We do have AppV here and tried that approach. While this gets us past the install minimum requirements, it does not resolve the issue of running of more than one instance at a time, per terminal server, even though our volume license allows for it.

Installing CR VS2010 on Windows 2008 Core Server

Hello,
We are attempting to re-build our web servers and reduce their footprint. In this effort we have chosen to use Windows 2008 Core Server with all of the web server installation features. In addition we upgraded our application to CR for VS2010 after finding that it supported Windows Server 2008. However, while trying to deploy the MSI packages to the server we are encountering the following error.
MSI PACKAGE
CRRuntime_32bit_13_0_1.msi
ERROR
Error 1904. Modeule C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\pageobjectmodel.dll failed to register. HRESULT -2147024770
SYSTEM INFORMATION
OS Name:                   Microsoft Windows Server 2008 R2 Standard
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:
Product ID:                00477-001-0000421-84205
Original Install Date:     4/27/2011, 10:12:31 AM
System Boot Time:          9/27/2011, 9:47:41 AM
System Manufacturer:       Microsoft Corporation
System Model:              Virtual Machine
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 44 Stepping 2 GenuineInt
el ~3058 Mhz
BIOS Version:              American Megatrends Inc. 090004 , 3/19/2009
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume4
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-08:00) Pacific Time (US & Canada)
Total Physical Memory:     1,536 MB
Available Physical Memory: 1,031 MB
Virtual Memory: Max Size: 3,840 MB
Virtual Memory: Available: 3,316 MB
Virtual Memory: In Use:    524 MB
Hotfix(s):                 32 Hotfix(s) Installed.
                           [01]: KB2425227
                           [02]: KB2446710
                           [03]: KB2476490
                           [04]: KB2478662
                           [05]: KB2503665
                           [06]: KB2506014
                           [07]: KB2506212
                           [08]: KB2506223
                           [09]: KB2507618
                           [10]: KB2507938
                           [11]: KB2508429
                           [12]: KB2509553
                           [13]: KB2510531
                           [14]: KB2511455
                           [15]: KB2518869
                           [16]: KB2524375
                           [17]: KB2525694
                           [18]: KB2533552
                           [19]: KB2534366
                           [20]: KB2536275
                           [21]: KB2536276
                           [22]: KB2539635
                           [23]: KB2552343
                           [24]: KB2555917
                           [25]: KB2556532
                           [26]: KB2560656
                           [27]: KB2563894
                           [28]: KB2567680
                           [29]: KB2570791
                           [30]: KB2570947
                           [31]: KB2616676
                           [32]: KB976902
INSTALLED PACKAGES
Name=Microsoft ASP.NET 2.0 AJAX Extensions 1.0
Name=SolarWinds Log Forwarder for Windows
Name=Microsoft Visual C++ 2005 Redistributable
Name=Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022
Name=Microsoft .NET Framework 4 Extended
Name=Microsoft .NET Framework 4 Client Profile
Any insight you can provide on the issue would be appreciated.
Thanks,
Phil

The DLLS that fail to register are:
pageobjectmodel.dll
reportrenderer.dll
PageObjectModel.dll is missing the following dependencies:
MSVCR80.DLL
OLEDLG.DLL
DEVMGR.DLL
EFSADU.DLL
NETPLWIZ.DLL
RASAPI32.DLL
RASDLG.DLL
SHDOCVW.DLL
TAPI32.DLL
ReportRenderer.dll is missing the following dependencies:
MSVCR80.DLL
OLEDLG.DLL
DEVMGR.DLL
EFSADU.DLL
NETPLWIZ.DLL
RASAPI32.DLL
RASDLG.DLL
SHDOCVW.DLL
TAPI32.DLL
If I ignore the registration errors the installer completes. When I run my application I get the following error:
The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception. >>> Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
Do we need to run the full version of Windows Server 2008 for this to work? I have installed the required VC++ run-time dependencies and still no luck.

Windows 2008 Terminal Server issue after swapping modem/router

Similar Messages

Maybe you are looking for