Cross Installation

Hi
everyone
I have installed oracle database 11g on my pc and recently installed oracle developer suite 10g
I am unable to connect to my database using oracle developer suite It's giving an error that
"ORA-12154:TNS could not resolve the connect identifier specified"
How to solve this problem or can't we connect to database using older version of suite
Kindly answer me this question as soon as possible
Thanks,

hi which operating system is this is Linux or window
did you try set ORACLE_SID=sid
set ORACLE_HOME=/ORACLEHOME
what is the status of LSNRCTL
can you show us your
path or your set
by going to your cmd command line

Similar Messages

10.4.8 cross installation

I recently purchased a MacBook with OS 10.4.8. Is it legal to install that OS in my G5 presently using 10.3.9? If so, how is that done?

Hi Conrad!
In a word, no.
Additional info in these links.
Using OS X Install CDs/DVDs On Multiple Macs In which, you will find a link to the Single User Software License Agreement.
What's A Computer Specific Mac OS X Release
Software Update, Upgrade: What's The Difference?
ali b

Can Not Install Mac OS X on this computer (MacBook)

Puzzles me: Brand new refurb. MacBook with 10.5 installed.
Repartitioned the drive to get two partitions and tried to use my Full Retail OS 10.5 disk to re-install.
Get error after the language selection: cannot install Mac OS X on this computer...
Same thing if I restart with an external drive and try to install from the retail disk to the MacBook's drive. I just can't imagine why I need to use the included machine specific disks instead of the retail version. I know it works if I take the drive out and mount it via FireWire to another Mac.
So what gives?

Your other answer had probably in the sentence.
I looked but could not find it so, as I remember, when Leopard retail came out with all the drivers and libraries for both PPC and Intel and some users were trying to install Tiger on new Leopard MacBooks and, like me, other cross installs, Apple released a short note that said only the install disk would work on the MacBook, not the retail. No reason was given. You have a better life because of it and your computing life is richer too.
Research Apple Partition Map and GUID. Do what you know works.

Cross-platform installs or upgrades

If I understand the license agreement correctly (and correct
me if I'm wrong), I'm able to install my copy of DW (and the rest
of the Suite) on both my PC and on my laptop, provided I don't use
them both at the same time. That's also provided that both my PC
and my laptop are on the same platform. I have a Windows PC and a
Mac laptop, so I'm out of luck. It seems a little unfair, and I
know there must be some kind of anti-piracy thing that they don't
allow this, but is there any consideration for changing this so us
legitimate users can do cross-platform installs without having to
purchase a second copy of the suite?

easthollow wrote:
> I have a
> Windows PC and a Mac laptop, so I'm out of luck. It
seems a little unfair, and
> I know there must be some kind of anti-piracy thing that
they don't allow this,
> but is there any consideration for changing this so us
legitimate users can do
> cross-platform installs without having to purchase a
second copy of the suite?
Your understanding of the licence agreement is correct. The
question of
a dual platform licence is raised in this forum on a regular
basis
because many indpendent developers are in the same situation.
However,
the answer is no - the licence is for one operating system
only.
At the moment, the Studio 8 CD-ROM contains both Mac and
Windows
versions, but I suspect that this may not always be the case.
Adobe
software is sold on separate disks.
I raised the question of dual licensing with an Adobe
executive at Adobe
Live in London a few months ago. He was sympathetic to the
problems of
an individual developer, but from the business point of view
the
situation was clear. It costs twice as much to create
programs for both
Windows and OS X, so if you want to use it on both systems,
you must
contribute towards both sets of development costs.
If you need to run the Windows version on your Mac, you can
always use
Virtual PC or one of the dual boot methods.
David Powers
Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
http://foundationphp.com/

"shared memory realm" error -- cross-posted in "installation"

I've just installed 8.1.7 on a Solaris 8 workstation. The installation went fine up until the database creation assistant tried to create a database: it failed. But the software was all installed, so I did a "connect internal" and created a database myself. Once I start the database, I can connect as system/manager; but when the database is shutdown, connecting as system manager gives me an "Oracle not available" error (ORA-01034) followed by a "shared memory realm not available" error (ORA-27101) followed by a "no such file or directory" error (SVR4 Error: 2:).
All of the shared memory and semaphore parameters are specified in the /etc/system file, and they show up when I execute a "sysdef -i" command.
Any ideas why I'm getting these errors?
I did a search and found a few posts on "shared memory realm," but none of them seemed to address the fact that I can connect when the database is started/mounted, but not when it's shutdown.
Thanks in advance,
Rich

make sure the env var ORACLE_SID is set.
check PROCESSES in your init.ora file. if you lower this number (to say, 15) and errors go away then you need to up the semiphores kernel parameter (or leave PROCESSES set to a low number). Also, it is correct to get an error when trying to connect to a database that is shutdown. the only way to not get an error is use svrmgrl or "sqlplus /nolog" and then connect / as sysdba (or connect internal).
Andrew

Re: Java Media Framework cross platform installation / setup on Mac / UNIX

JMF cross-platform doesn't support everything that the native performance pack versions support. I found this out the hard way too because pure Java JMF can't play AVI's from my digital camera but the Win32 enhanced JMF can. In particular, with my case pure Java JMF doesn't support all the frame rates that the others do.
I know Apple has been releasing some of the other APIs lately, like JAI. We might want to check over at apple.com and see if they have a native JMF impl.

Hi,
JMF work well on OS(32bits) and Java(32bits)
Octavian.
Edited by: user7659448 on Feb 28, 2012 10:42 AM

IFS installation - cross platform

I would like to install iFS software installed on NT and repository on Solaris.
If yes where can I find more information
about this?

Hello.
As Jaikishan mentions, you can install iFS on Windows NT, and the Oracle database (where iFS stores its data) on a Solaris box.
However, Jaikishan meant to say that you access your data through SQL*Net (JDBC), not SQL Views.
To get more information, refer to the iFS 1.1 for NT Installation Guide, chapter 1, where it gives the requirements for "installing Oracle iFS on a separate computer from Oracle8i" (such as installing the Oracle8i client on the NT box).
See in particular pages 1-6 through 1-9.
I hope that helps.

Cross Country Installation

I live in South Africa, can I purchase and download Adobe Photoshop CS6 on Newegg (USA)? Will the licence work because I am in a different country?

thanks so much

Cross platform installation

I need to download Digital Editions for Pocket PC ( Windows Mobile 2003 second ed.), but at the moment I can only connect my Mac Powerbook to the net. I then plan to transfer it to my PDA.
I have installed Digital Editions on the powerbook and it works fine.
Any advise would be gratefully received.
Ian

Many thanks Jim,
I was getting really tired of trying different approaches to this one.
Guess that I'll stick to Mobipocketbook for now.
Thanks again
Ian

Cross-Hardware Installation

In theory is it possible to install the version of OS 10.4 that comes with a PowerBook into a G5 Desktop PowerPC, or are the discs that come with these computers "computer specific"?
Thanks in advance.

...and the license agreement allows you to only use them with the Mac that they shipped with.

Troubleshoot installation problems in Photoshop Lightroom on Windows Vista

This document can help you to resolve system errors that occur while you use Adobe Photoshop Lightroom on Windows Vista. System errors can manifest in many different ways, including (but not limited to) the following:
A blank or flickering dialog box
A frozen cursor or screen
A blue screen
An unexpected restart
An error message such as:
"Setup is unable to load the installation script file."
"Unable to create a directory under C:\Windows\System. Please check write-access to the directory."
"Uninstalling: C:\Program Files\Adobe\Adobe Photoshop Lightroom refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location."
Note: If you attempt to install Photoshop Lightroom to a drive that doesn't have the minimum required space available, the installation will fail. You must then completely reinstall to another location that has sufficient free space.
Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with Photoshop Lightroom, Photoshop Lightroom may not necessarily be the cause; it may be the only application that uses enough memory or processor cycles to expose the problem.
To benefit most from this document, perform the tasks in order. Keep track of the tasks that you perform and the results of each, including errors and other problems. Adobe Technical Support can use this information to better assist you if you need to call.
You must be logged on as an administrator to perform some of the procedures in this document.
Important: Some of the procedures in this document may initiate a User Access Control dialog that asks for your permission to continue. Read the details in the dialog to determine if you want to continue. If you choose to cancel the dialog, then you will not be able to continue with that troubleshooting step.
The steps in this document that refer to the Control Panel are in reference to the Classic view. For information on switching the Control Panel to the Classic view and many other common OS procedures, see Common Microsoft Windows Vista procedures (TechNote kb401275)
Some of these procedures require you to locate hidden files and hidden folders. Some procedures require you to locate files by their full file names, which include extensions (for example, example_filename.ini). By default, Windows Explorer doesn't show hidden files, hidden folders, and file name extensions that it recognizes.
To show hidden files, hidden folders, and all file name extensions in Windows Explorer:
In Windows Explorer, choose Organize > Folder And Search Options.
Click the View tab in the Folder Options dialog box.
In Advanced Settings, select Show Hidden Files And Folders.
Deselect Hide Extensions For Known File Types.
Click OK.
Note: The procedures in this document are based on the default interface of Windows Vista. If the interface is customized, some procedures may vary. For example, a commonly encountered difference is the navigation to Control Panel from the Start menu: You may navigate Start > Settings > Control Panel instead of Start > Control Panel. Additionally, the procedures in this document assume you are using the Classic View of the Control Panel: To view the Control Panel in the Classic View, click Switch To Classic View on the Control Panel navigation bar on the left side of the window.
Beginning troubleshooting
The tasks in this section can help you resolve the most common system errors. Before performing any of these tasks, back up all personal files (for example, Photoshop Lightroom files you created). Always restart the computer after a system error occurs to refresh system memory. Continuing to work without restarting the computer may compound the problem.
1.Make sure that the system meets the minimum requirements for PhotoshopLightroom.
Photoshop Lightroom may not run correctly on a system that doesn't meet the following requirements:
Intel Pentium 4 or equivalent processor
Microsoft Windows XP, Windows Vista, Windows 7
768 MB of RAM (1 GB recommended)
1 GB of available hard-disk space
CD-ROM drive
In addition to these requirements, a video card that supports 24-bit (16 million) or more colors, and a resolution of 1024 x 768 or higher, is recommended.
* Photoshop Lightroom 1.0 will install and run on Windows Vista but Adobe cannot guarantee the quality of the software experience until Adobe fully certifies Photoshop Lightroom for use on Windows Vista.
To check basic system information, such as processor speed and how much RAM is installed, choose Start > Control Panel > System.
2. Delete previously installed application files, especially if you had the public beta version of Photoshop Lightroom installed.
To delete files from a previous Adobe Photoshop Lightroom installation attempt:
Choose Start > Control Panels > Add or Remove Programs.
Select Adobe Photoshop Lightroom and choose to remove it.
Close the Add Or Remove Programs window and the Control Panel.
Open Windows Explorer.
If the Lightroom.exe file is still in the Program Files\Adobe\Adobe Photoshop Lightroom folder, delete it.
If the Lightroom Preferences.agprefs file is still in the Documents and Settings/[username]/Application Data/Adobe/Lightroom/Preferences folder, delete it.
Empty the Recycle Bin.
Try to reinstall. If you cannot, continue with the next two sections in this step:
Move all the folders under the Users/[username]/AppData/Roaming/Adobe/Lightroom folder into a new folder on the desktop; name the folder Lightroom Presets. These are the presets that were installed with the application and that you created.
Move all the folders under the Users/[username]/Pictures/Lightroom/Lightroom Previews.lrdata folder into a new folder on the desktop; name the folder Lightroom Previews. If you have a large number of images, you can move this folder back to its original location before you open Photoshop Lightroom, once it's installed. Or you can delete this folders to re-create it when Photoshop Lightroom opens. If there are further problems with Photoshop Lightroom after it's installed, it might be due to corruption in the previews, in which case you need to delete this folder and re-create it.
Try to reinstall.Important: Do not delete the Lightroom Database.lrdb file!
If there are further problems with Photoshop Lightroom after it's installed, these issues may be due to corruption in the preset files you created, in which case you need to remove them and re-create them, or test each preset individually.
Note: If you can reinstall, and if this is not the first time you opened Photoshop Lightroom, then Photoshop Lightroom will look for a library database file. If it does not find a library in the expected location, it will prompt you to create a new library, locate the library, or exit. Exit will close the dialog box, and Photoshop Lightroom will not open. Although you can tell Photoshop Lightroom to locate your library, it's best to put it back in the default location and then open the application.
If you can reinstall, close Photoshop Lightroom and then copy any presets you created from the Lightroom presets on the desktop back into the Users/[username]/AppData/Roaming/Adobe/Lightroom folder.
If you cannot reinstall, then move the Lightroom Database.lrdb file from the Users/[username]/Pictures/Lightroom folder into a new folder called Lightroom Database File and save this file on the desktop. This is your database, if you previously had Photoshop Lightroom installed.
Reinstall Photoshop Lightroom. If you cannot reinstall, continue with the next task in this document.
3. Log in as Administrator before installingPhotoshopLightroom.
In Windows Vista, you must be logged in with local (that is, machine) Administrator rights to install Photoshop Lightroom. If you don't have administrator rights, contact your system administrator for assistance.
4. Check the CD and CD-ROM drive.
Dust or dirt on a CD can interfere with an installation and prevent the CD-ROM drive from recognizing the CD. Examine the Photoshop Lightroom CD for dirt, dust, or fingerprints. Gently wipe the bottom of the CD from the center outward with a soft, lint-free cloth.
Verify that the CD-ROM drive can read other CDs. If it can't, examine the CD caddy or loading tray for dirt, and clean it with a lint-free cloth. If it still can't read other CDs, contact the CD-ROM drive manufacturer or the computer manufacturer.
5. Install current Windows service packs and other updates.
Updates to the Windows operating system improve its performance and compatibility with applications. You can obtain Windows service packs and other updates from the Microsoft website at www.windowsupdate.com. For assistance installing service packs and other updates, contact Microsoft technical support.
Important: Before you install a system update, check the system requirements for Photoshop Lightroom (and any third-party software or hardware you may use with Photoshop Lightroom ) to ensure compatibility. If the update isn't listed, then contact Adobe or the manufacturer of your third-party software or hardware.
6. InstallPhotoshopLightroomfrom the desktop and use the default installation folder.
Some system components such as device drivers and virus protection utilities can conflict with the Photoshop Lightroom installer and result in an incomplete or failed installation, or they can cause problems when you install to a folder or when you use a path to the default installation folder that contains a special character, such as #. To prevent these conflicts, install Photoshop Lightroom from the desktop, and use the default folder name and path.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
7.Re-create thePhotoshopLightroompreferences file.
Re-create the Photoshop Lightroom preferences file to eliminate problems that a damaged preferences file might cause:
Quit Photoshop Lightroom.
Rename the Lightroom Preferences.agprefs file (for example, to Lightroom Preferences.old) in the Users/[username]/AppData/Roaming/Adobe/Lightroom/Preferences folder.
Start Photoshop Lightroom. Photoshop Lightroom creates a new preferences file.
If the problem continues, the preferences file isn't the cause. To restore custom settings, delete the new preferences file and restore the original name of the previous preferences file.
8.Install and run Photoshop Lightroom while no other applications are running.
Some applications may interfere with installing or running Photoshop Lightroom. Virus protection programs are meant to stop viruses from installing on your computer. Before installing or starting Photoshop Lightroom, disable other applications, including virus protection programs and startup items (items that start automatically with Windows).
To disable startup items and non Microsoft services:
Quit all applications.
Choose Start, type msconfig in the Search text box, and press Enter.
Write down all unselected items under the Startup and Services tabs.
Click the General tab, and choose Selective Startup.
Click the Startup tab and select Disable All.
Click the Services tab and select Hide All Microsoft Services.
Select Disable All then re-select FLEXnet Licensing Service. If you are unsure whether an item is essential, then leave it deselected (disabled).
Click Apply, and restart Windows for the changes to take effect.
Note: Upon restart, you'll be notified that the System Configuration utility has made changes to the way that Windows starts up. Click OK. When the System Configuration utility appears, click Cancel.
Right-click icons in the Notification Area and close or disable any startup items that are still active.
9. Install Photoshop Lightroom to a different hard disk after disabling startup items and installing from the hard disk.
Hard disk problems can prevent Photoshop Lightroom from installing correctly. By installing Photoshop Lightroom to a different physical hard disk, you can verify if the original hard disk is preventing installation. First, completely remove Photoshop Lightroom from the hard disk.
To install Photoshop Lightroom to a different hard disk after disabling startup items:
Follow the steps in task 8 above to disable startup items.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
Click Change and select a different hard disk in the Change Current Destination Folder window. Click OK, and then follow the on-screen instructions.
Intermediate troubleshooting
If the tasks in the previous section don't solve the problem, try the following intermediate troubleshooting tasks.
10. Install and run Photoshop Lightroom in a new user account.
Create a new user account that has the same permissions as the account that you use when the problem occurs. If the problem doesn't recur, the original user account may be damaged. For instructions on creating a new user account, see To add a new user to the computer in Windows Help or contact your system administrator.
11. Optimize handling of temporary files by Windows Vista.
Windows and applications store working data in temporary (.tmp) files that they create on the hard disk. Excessive or outdated temporary files can interfere with performance of Windows or applications.
Delete temporary files by using the Disk Cleanup utility included with Windows or by using the following instructions. Make sure that at least 1 GB of free space is available on the hard disk to which temporary files are written. To start Disk Cleanup, choose Start > All Programs > Accessories > System Tools > Disk Cleanup. For information about Disk Cleanup, see Windows Help.
To manually delete temporary files:
Note: Windows deletes temporary files when Windows and applications close normally. However, when Windows or an application crashes, temporary files can accumulate on the hard disk. Windows may prevent you from deleting some temporary files as they may be in use. Delete as many temporary files as you possibly can, without deleting the files that are in use.
Quit all applications.
Choose Start and type %tmp% in the Search text box and press Enter.
Delete the contents of this folder.
Note the drive letter where this directory is located.
To ensure that at least 1 GB of free space is available on the hard disk to which temporary files are written:
Choose Start > My Computer.
Select the drive noted in step 4. Right click and select Properties.
Confirm the drive has at least 1 GB of free space.
12. Repair and defragment hard disks.
System errors can occur if hard disks contain damaged sectors or fragmented files. Repair and defragment hard disks, either by using the Error-checking tool and Disk Defragmenter utility included with Windows or by using a third-party disk utility. You should run such utilities on each hard disk or partition. More information about the Error-checking tool and Disk Defragmenter appears below; for more information about a third-party disk utility, refer to the documentation for the utility.
The Error-checking tool repairs bad sectors, lost allocation units and file fragments, cross-linked files, and invalid file names. To access the Error-checking tool, choose Start > Computer, right-click the desired hard disk, and choose Properties from the menu. In the Local Disk Properties dialog box, click the Tools tab, and then click Check Now in the Error-checking area.
Note: To prevent Disk Defragmenter from moving files to bad sectors of a disk, run the Error-checking tool before running Disk Defragmenter.
Disk Defragmenter rearranges the files and free space on your computer so that files are stored in contiguous units and free space is consolidated in one contiguous block. To access the Disk Defragmenter utility, choose Start > All Programs > Accessories > System Tools > Disk Defragmenter.
13. Scan the system for viruses.
Use current anti-virus software to check the system for viruses. Virus infections can damage software and cause system errors. For more information, see the documentation for the anti-virus software.
14. Try to install Photoshop Lightroomon a different computer.
Try to install Photoshop Lightroom on a different computer to determine if the problem is unique to your computer. If the problem is unique to your computer, contact the computer manufacturer; if the problem occurs on multiple computers, contact Adobe Technical Support.
Advanced Troubleshooting
If the tasks in the previous section don't resolve the problem, you may be able to resolve the problem by reinstalling Windows Vista and Photoshop Lightroom, reformatting your hard disk and reinstalling Windows Vista and Photoshop Lightroom, or by determining if hardware is conflicting with Photoshop Lightroom.
Disclaimer: Adobe doesn't support hardware and provides these procedures as a courtesy only. For further assistance, contact the hardware manufacturer or an authorized reseller. If you troubleshoot hardware problems yourself, you may void the warranty for your computer.
Note: Before you remove or rearrange hardware, turn off and disconnect power to the computer and any peripheral devices.
15. Log in using the built-in Administrator account.
The built-in Administrator account has a higher access level to the system than a normal local administrator account. By default the built-in Administrator account is disabled. For information about enabling and logging in to the built-in Administrator account, contact your system administrator. You can also refer to this support document on the Microsoft support website: http://support.microsoft.com/kb/926183/en-us?spid=11737&sid=73.
16. Reformat the hard disk, and reinstall only Windows Vista and Photoshop Lightroom.
Reformat the hard disk, and then install only Windows Vista and Photoshop Lightroom from the original installation media. Reformatting a disk erases all files it contains, so be sure to back up all personal files first. Also make sure that you have all application and system disks.
For instructions on performing a clean installation of Windows Vista, see document 918884, "How to install Windows Vista" on the Microsoft website at http://support.microsoft.com.
Note: Don't install additional software or hardware until you're sure that the problem is resolved. Don't back up the hard disk and restore Windows and Photoshop Lightroom instead of reinstalling them. If the problem is caused by an application or Windows, and either one is restored instead of reinstalled, the problem may recur.
After you reformat the hard disk and reinstall Windows and Photoshop Lightroom, try to re-create the problem:
If the problem no longer occurs, then install other applications one at a time and try to re-create the problem after each installation. If the problem occurs after an installation, then the recently installed application may be the cause.
If the problem occurs when only Windows and Photoshop Lightroom are installed, then the cause may be hardware-related, and you should contact the hardware manufacturer or an authorized reseller for assistance.
17. Check for problems with RAM modules.
Ensure that the RAM modules are installed properly and are not the cause of your problem. Do one or both of the following:
Change the order of the installed modules.
Remove all but the minimum number of modules needed to run Windows and [product], and test to see if the problem persists. If it does, replace the modules you removed and remove the others, testing again to see if the problem recurs. If it doesn't, then one or more of the removed modules are the cause. For assistance, contact the RAM manufacturer.

You've tried Help>Updates from within photoshop cs6?
Or this 8.3 updater
http://swupdl.adobe.com/updates/oobe/aam20/win/PhotoshopCameraRaw7-7.0/8.3.52/setup.zip
If that doesn't work, you can install camera raw 8.3 by following the directions on the following page
Adobe Camera Raw Help | Camera Raw/DNG Converter 8.4 on Mac OS 10.6, Windows XP, and Vista

SAP GUI 730 PL8 Installation Problems

Hi all!
We are facing a problem with the following software product:
Information NwSapSetupAdmin.exe:
SAP GUI for Windows 7.30 (Compilation 3)
Component ID: 1460620d-c8bc-44c2-86ec-e632e0986b01
Version: 27625
Latest Patch Level: 8
SAP Automatic Workstation Update
Component ID: 40d11884-3906-4e67-8a96-91035ca09814
Version: 900.42
Latest Patch Level: 45 Version 9.0.45.0
Information SAP Logon:
Release: 730 Final Release
Dateiversion: 7300.3.8.1084
Build: 1478436
Patch-Level: 8
Within the SAP GUI Installation (NwSapSetup.log) the following error occurs:
16:25:13 NwSapsAtlC 1   Executing script action...
16:25:13 NwSapsAtlC 1   Script-action: Checking reboot condition.
16:25:13 NwSapsAtlC 1   Script-action: NwEngine.Context.Reboot = 1
16:25:13 NwSapsAtlC 1E Microsoft VBScript runtime error: Error message: Unknown error 0x800A01B6. Error code 0x800a01b6.
                         Object doesn't support this property or method: 'NwEngine.Context.Args' (Line 4, Col. 5)
                         The setup script contains the error listed above. Please contact your system administrator and provide this information, for example by sending him a screenshot of this message box (Press Alt+PrtScrn to create the screenshot and copy it to the clipboard).
16:25:13 NwSapsAtlC 1E Failed to run script:
                              ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
                           1: NwEngine.Context.Log.Write "Script-action: Checking reboot condition."
                           2:             NwEngine.Context.Log.Write "Script-action: NwEngine.Context.Reboot = " & NwEngine.Context.Reboot
                           3:             If NwEngine.Context.Reboot = 1 Then
                           4:                 If NwEngine.Context.Args("SuppressReboot") <> "" Then
                           5:                     NwEngine.Context.Reboot = 0    'Setting Flag for no Reboot
                           6:                     NwEngine.Context.Log.WriteWarning "Script-action: Reboot suppressed by the user. NwEngine.Context.Reboot = " & NwEngine.Context.Reboot
                           7:                 ElseIf NwEngine.Context.Args("DelayReboot") <> "" Then
                           8:                     NwEngine.Context.Reboot = 1    'Setting Flag for delayed Reboot
                           9:                     NwEngine.Context.Log.WriteWarning "Script-action: Reboot delayed by the user. NwEngine.Context.Reboot = " & NwEngine.Context.Reboot
                          10:                 Else
                          11:                     NwEngine.Context.Reboot = 2    'Setting Flag for immediate Reboot
                          12:                     NwEngine.Context.Log.Write "Script-action: Enforce immediate reboot."
                          13:                 End If
                          14:             End If
                              ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
                         Error message: Unknown error 0x80020101. Error code 0x80020101.
16:25:13 NwSapsAtlC 1E Failed to parse script. Error message: Unknown error 0x80020101. Error code 0x80020101.
16:25:13 NwSapsAtlC 1E While processing Component '$MS System Files' with Id '{F270A214-3AD3-4235-9C74-F4D323B54976}' 1 error(s) have been registered.
16:25:13 NwSapsAtlC 1   CompAct.:Installed Component '$MS System Files' with Id '{F270A214-3AD3-4235-9C74-F4D323B54976}'
With this the NwSapSetup.log ends with:
16:26:23 NwSapSetup 1 Return-Code: 145
In the next logical step within our environment a uninstallation of the SAP GUI gets started:
   Commandline:
'"C:\Program Files (x86)\SAP\SapSetup\Setup\NWSapSetup.exe" /Silent /Uninstall /Package=PEACY'
This operation gets done with:
12:35:47 NwSapSetup 1 Return-Code: 0
After that the installation of the SAP GUI gets started again with:
   Commandline:        '"C:\peacy.sys\source\SAPGUI730PL8\source\setup\NwSapSetup.exe" /noDLG /norestart /Package=PEACY'
Now the Installation gets done with:
12:52:12 NwSapSetup 1 Return-Code: 0
Every first installation of SAP GUI 7.30 PL8 is affected. This is a cross-platform issue (Windows 7 and Windows 8.1). If there was our older package version (SAP GUI 7.30 PL4) installed, the installation of SAP GUI 7.30 PL8 gets done without problems.
Every new client with the SAP GUI 7.30 PL8 assigned or the re-installation of it, and every first installation of the package on a client without SAP GUI leads to the mentioned issue - package gets installed with the mentioned error, afterwards the uninstallation gets started by our environment and finally the installation gets done with the second try. This is not a practicable method for our support staff.
Are there any hints how to resolve this issue. (A upgrade to the newest patch level of SAP GUI is not a practicable solution)
Thanks in advance!
Best regards
Christian

Hello Christian,
For older releases of the SAP GUI client a good approach is to create package for uninstalling old SAP GUI. Depending on the state of the old SAP GUI's you're upgrading those may not be "clean" enough to warrant upgrading in place.
The older GUI's have component's no longer provided with the newer releases so most recommendations are to uninstall completely an do a fresh installation.
I credit Matt Fraser for this information and suggest reading his documentation. The last 4 articles are germane to you're situation. I hope this helps you.
http://scn.sap.com/thread/3620515
http://scn.sap.com/docs/DOC-55477
http://scn.sap.com/docs/DOC-55574
http://scn.sap.com/docs/DOC-55575
http://scn.sap.com/docs/DOC-55633
http://scn.sap.com/docs/DOC-55634
http://scn.sap.com/docs/DOC-55674
Cheers,
Dan Mead

Installation problem with KM collaboration

Dear All,
I am trying to install KM on WEBAS 6.4 patch 9.
I am using master CD to start SAP INSt.. then i specify location for NW Component CD and give user logon details.. it starts installation, but in second step itself. it gives error:
ERROR 2006-02-06 12:41:51
FJS-00003 TypeError: node has no properties (in script InstallationScript_32, line 12683: ???)
Can you please suggets is i am missing something here..
I am attaching detail of log:
INFO 2006-02-06 12:38:56
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: q0w9e9r8t7.1.xml.
INFO 2006-02-06 12:38:56
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: q0w9e9r8t7.1.xml.
INFO 2006-02-06 12:38:56
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\q0w9e9r8t7.1.xml.
INFO 2006-02-06 12:38:57
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.1.xml.
INFO 2006-02-06 12:38:57
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.xml to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/keydb.1.xml.
INFO 2006-02-06 12:38:57
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\keydb.1.xml.
INFO 2006-02-06 12:38:58
Installation start: Monday, 06 February 2006, 12:38:56; installation directory: C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC; product to be installed: SAP NetWeaver '04 Support Release 1> NetWeaver Components Running on Java> Content Management and Collaboration> Content Management and Collaboration Installation
INFO 2006-02-06 12:39:07
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.log.
INFO 2006-02-06 12:39:08
Output of C:\j2sdk1.4.2_08\jre/bin/java '-version' is written to the logfile java.log.
INFO 2006-02-06 12:39:08
Execution of the command "C:\j2sdk1.4.2_08\jre/bin/java '-version'" finished with return code 0. Output: java version "1.4.2_08"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
INFO 2006-02-06 12:39:08
Looking for SAP system instances installed on this host...
INFO 2006-02-06 12:39:10
Found these instances: sid: NWD, number: 01, name: SCS01, host: chn-mumsap02sid: NWD, number: 00, name: DVEBMGS00, host: chn-mumsap02
INFO 2006-02-06 12:39:22
Looking for SAP system instances installed on this host...
INFO 2006-02-06 12:39:24
Found these instances: sid: NWD, number: 01, name: SCS01, host: chn-mumsap02sid: NWD, number: 00, name: DVEBMGS00, host: chn-mumsap02
INFO 2006-02-06 12:39:24
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.log to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.1.log.
INFO 2006-02-06 12:39:24
Copying file C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.log to: C:/Program Files/sapinst_instdir/NW04SR1/CMC/KMC/java.1.log.
INFO 2006-02-06 12:39:24
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.1.log.
INFO 2006-02-06 12:39:24
Removing file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.log.
INFO 2006-02-06 12:39:24
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\java.log.
INFO 2006-02-06 12:39:24
Working directory changed to G:/Comp/EP-KMC/ANALYZER.
INFO 2006-02-06 12:39:24
Working directory changed to C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC.
INFO 2006-02-06 12:39:24
Output of C:\j2sdk1.4.2_08\jre/bin/java '-classpath' 'G:/Comp/EP-KMC/ANALYZER/analyzer.jar;E:/usr/sap/NWD/DVEBMG1/j2ee/cluster/server0/bin/ext/SAPXML1/SAPXML~1.JAR' '-Dj2ee.path=E:\usr\sap\NWD\DVEBMGS00\j2ee' '-Dj2ee.userName=j2ee_admin' 'XXXXXX' '-DMainClass=com.sapportals.utilities.analyzer.ui.console.MainConsole' '-DappendRelativePath=E:\usr\sap\NWD\DVEBMGS00\j2ee' 'com.sapportals.utilities.analyzer.ui.Launcher' 'C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC/analyzerResults.htm' '-e' '/' '-i' 'KMC/Portal Existence' is written to the logfile java.log.
INFO 2006-02-06 12:39:26
Execution of the command "C:\j2sdk1.4.2_08\jre/bin/java '-classpath' 'G:/Comp/EP-KMC/ANALYZER/analyzer.jar;E:/usr/sap/NWD/DVEBMG1/j2ee/cluster/server0/bin/ext/SAPXML1/SAPXML~1.JAR' '-Dj2ee.path=E:\usr\sap\NWD\DVEBMGS00\j2ee' '-Dj2ee.userName=j2ee_admin' 'XXXXXX' '-DMainClass=com.sapportals.utilities.analyzer.ui.console.MainConsole' '-DappendRelativePath=E:\usr\sap\NWD\DVEBMGS00\j2ee' 'com.sapportals.utilities.analyzer.ui.Launcher' 'C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC/analyzerResults.htm' '-e' '/' '-i' 'KMC/Portal Existence'" finished with return code 0. Output: file:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/appclient/appclient.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/boot/boot.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/bytecode.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/configuration/configuration.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/cross/cross_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/dbpool/dbpool.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/dispatcher/bin/system/exception.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/frame.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/iq-lib.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/boot/jaas.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/log/log_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/logging.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/naming/naming.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/p4/p4.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/ext/sapxmltoolkit/sapxmltoolkit.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/security/security.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/security/security_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/system/util.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/services/deploy/deploy.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/cluster/server0/bin/interfaces/container/container_api.jarfile:/E:/usr/sap/NWD/DVEBMGS00/j2ee/admin/lib/admin.jar
INFO 2006-02-06 12:39:26
Looking for SAP system instances installed on this host...
INFO 2006-02-06 12:39:28
Found these instances: sid: NWD, number: 01, name: SCS01, host: chn-mumsap02sid: NWD, number: 00, name: DVEBMGS00, host: chn-mumsap02
INFO 2006-02-06 12:39:53
RFC parameter CLIENT set to value 000.
INFO 2006-02-06 12:39:53
RFC parameter USER set to value DDIC.
INFO 2006-02-06 12:39:53
RFC parameter LCHECK set to value 1.
INFO 2006-02-06 12:39:53
RFC parameter PCS set to value 1.
INFO 2006-02-06 12:39:53
RFC parameter LANG set to value EN.
INFO 2006-02-06 12:39:53
RFC parameter ASHOST set to value chn-mumsap02.
INFO 2006-02-06 12:39:53
RFC parameter SYSNR set to value 00.
INFO 2006-02-06 12:39:53
RFC connection is logged in file 'rfc#####_#####.trc'.
INFO 2006-02-06 12:39:53
RFC parameter TRACE set to value 1.
INFO 2006-02-06 12:39:53
RFC connection information checked successfully.
INFO 2006-02-06 12:39:53
RFC connection opened successfully.
INFO 2006-02-06 12:39:53
Setting new application function RFC_SYSTEM_INFO.
INFO 2006-02-06 12:39:53
Generating interface for remote function.
INFO 2006-02-06 12:39:53
Function call was successful.
INFO 2006-02-06 12:39:53
Function interface generated successfully.
INFO 2006-02-06 12:39:53
Technical properties of function set successfully.
INFO 2006-02-06 12:39:53
Information for application function RFC_SYSTEM_INFO copied to local Repository.
INFO 2006-02-06 12:39:53
Function module RFC_SYSTEM_INFO set successfully.
INFO 2006-02-06 12:39:53
Executing function call RFC_SYSTEM_INFO.
INFO 2006-02-06 12:39:54
Function call was successful.
INFO 2006-02-06 12:39:54
Version 640 of remote SAP System NWD accepted.
INFO 2006-02-06 12:41:37
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\summary.html.
PHASE 2006-02-06 12:41:37
Deployment of Basis functionality for Integration Server
INFO 2006-02-06 12:41:38
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\msclients.exe.log.
INFO 2006-02-06 12:41:38
Working directory changed to C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC.
INFO 2006-02-06 12:41:38
Output of E:\usr\sap\NWD\SYS\exe\run/msclients.exe '-mshost' 'chn-mumsap02' '-msserv' '3601' is written to the logfile msclients.exe.log.
INFO 2006-02-06 12:41:42
Execution of the command "E:\usr\sap\NWD\SYS\exe\run/msclients.exe '-mshost' 'chn-mumsap02' '-msserv' '3601'" finished with return code 0. Output:
INFO 2006-02-06 12:41:42
Creating file C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC\jcmon.exe.log.
INFO 2006-02-06 12:41:42
Working directory changed to C:\Program Files\sapinst_instdir\NW04SR1\CMC\KMC.
INFO 2006-02-06 12:41:42
Output of E:\usr\sap/NWD/DVEBMGS00/j2ee/os_libs/jcmon.exe 'pf=E:\usr\sap\NWD\SYS\profile/NWD_DVEBMGS00_chn-mumsap02' is written to the logfile jcmon.exe.log.
INFO 2006-02-06 12:41:45
Execution of the command "E:\usr\sap/NWD/DVEBMGS00/j2ee/os_libs/jcmon.exe 'pf=E:\usr\sap\NWD\SYS\profile/NWD_DVEBMGS00_chn-mumsap02'" finished with return code 0. Output: snipped
ERROR 2006-02-06 12:41:47
FJS-00003 TypeError: node has no properties (in script InstallationScript_31, line 12683: ???)
<b>ERROR 2006-02-06 12:41:51
FJS-00003 TypeError: node has no properties (in script InstallationScript_32, line 12683: ???)</b>

Hi Robert,
Thanks for your reply.. but i was unable to find out
< step name="increaseAddServTimeout">
in my control.xml file..
any clue.. why this is missing.?
FJS-00003 TypeError: node has no properties (in script InstallationScript 304, line 3372: ???)
SOLUTION/WORKAROUND
1. In the sapinst error window, press "OK" to terminate sapinst.
2. Open the file <installation_dir>/control.xml with a text editor.
3. Search for the first occurance of the string
< step name="increaseAddServTimeout">
You should see the following piece of code:
<step name="increaseAddServTimeout">
<script include="UM,epHelpers"><![CDATA[
var targetdir = context.get("inqmy_installationDirectoryToBeU...
1. Add the following line (in one line !)
context. set("inqmy_instanceNameToBeUsed",new Table("t_context_for_InQMy").select("SAPSID", "WHERE ROWNUM = 0"));
o that the result looks as follows:

CS4 Master Collection trial installation blocks CD installation

Hi!
I'm need someone to help me. Here is a description of what happened, when I installed the Creative Suite (CS4) trial and tried to install the full version:
1) I installed the trial version of CS4 Master Collection from a CD because I didn't need the whole version (or so I thought at that point, I was stupid as seen later).
2) The installation screen told me I was able to insert the activation key later if I wanted. My impression was that I can do the installation and then upgrade to the full version if I wish.
3) I run through the installation smoothly. No errors occurred during the installation.
4) I could use the trial for 30 days after which the version expired.
5) Then I tried to upgrade to the full version using the CD activation key. Unfortunately, the key didn't work but rather showed a red cross and an error message popped up saying the activation key was "not valid".
6) My friend told me I should remove the trial version and then reinstall from the CD. However, the same problem also occurred in some other computers, so I believe that's not the only cause of the problem.
7) After spending some time on internet, I found the following blog dealing with the topic:
http://sherylcanter.com/wordpress/2009/02/problems-removing-and-installing-adobe-cs4/
I read some of the messages posted in the blog. I started searching for the cleaning tool mentioned in the blog, and finally found the tool from Adobe web:
http://www.adobe.com/support/contact/cscleanertool.html
I would really appreciate if someone with similar experience would tell, whether this tool really works in the latest versions of Windows (Vista, 7 & 8, I have 7).
I would also appreciate any assistance on the topic.
I already tested removing the "cache"-file from /C:/Program FIles/Common FIles/Adobe/Adobe PMC/cache/.. My effort had no effect.
If I really need to install my system again, will I lose all the files on the computer I'm using? I don't want to believe that. Probably I can store some of the most important files on an USB-memory and still be able to use the Suite when it's installed and the files returned to my computer? I surely need to backup the system on my PC and not the others that were connected to it (any additional backup would be a catastrophe )?
I'm sorry for all the stupid questions & stuff, but I'm trying to get my message as clear as possible.
CS4 is an expensive software, so I really need to get it work. Installing the Suite from a CD should be possible because anyone may have a trial on his PC before buying the full version on CD. That's the purpose of the trial version, I see.
Thank you for any help!

Thank you for a fast reply!
The problem is stated in the title of my previous message: I cannot install the full version because I installed the trial.
Formatted as a question: "How can I get the CD installed with the original serial number?"
You wrote: "And where did you actually buy your CS4 license? There's a lot of fakes out there..."
>The license belongs to my employee. I'm totally sure that the version I'm trying to install is not a fake.
"Other than that you could simply have used a wrong region installer for your trial and the serial number ranges are not compatible"
>Could you clarify that more. The Suite has worked perfectly before I installed the trial. The installer only asked me to accept the license agreement and to choose between the trial and the full install. I was not asked anything else.
"You lose yourself in lengthy descriptions without actualyl ever telling what the problem really is, what the exact text of the warnings/ error messages is, what exact system you are on and so on"
>I admit my "question" was lenghty and somewhat messy. Here are some more details:
Country: Finland
Operating system: Windows 7 (as mentioned earlier)
Computer: Fujitsu (all requirements of the Suite are fulfilled, as the trial worked well)
Exact error message: "The serial number you entered is not valid. Click OK to retry entering the serial number."
Situation: I installed the trial, waited 30 days, and the trial expired. After that I tried to insert the disk serial number.
Possible solutions: Removing the trial and installing from beginning.
Internet access: Was ON during the installation.
The program has installed correctly earlier. Even with the serial number put in the back side of the disk.
Right now I don't have the information of the place where the Suite was bought (probably the origin is not in Finland). I can find it out on Monday. Possibly it was bought used that would make tracking a bit difficult.
Please ask if anything is still unclear. I know more on Monday, so if you can specify what information is essential by then, I would appreciate, and come on Monday with the asked pieces of information.
Hope this message clarified something.

Cross-reference failure when converted to PDF

One of my clients uses FrameMaker 7.1 to author their product documents, and convert everything to PDF before releasing it. I often see problems where cross-references within the document work in FrameMaker, but do not work as links in PDF, even though they show as links and the cursor in Acrobat changes correctly as it should when pointing to a link. I have now encountered a FrameMaker file where the cross-references worked as links in the first revision of a PDF, but a random selection of them didn't in the next revision, even though no changes were made to any cross-references in the original FM file. It's not an issue with my PC or that of the person who generated the files - we have tried the conversion on multiple installations and they all produce the same result. To fix it we've had to locate each failed link in the PDF and put it right manually in the FM source file. Has anyone else encountered this? Any thoughts on the cause?

DxCooper (not your real name, I guess),
The rigid approach is to check in the PDF Setup dialog, last tab "Links", whether the option "Create Named Destinations for All Elements and Paragraphs" is selected. This helps but the size of the PDF may increase considerably.
Another thing which may help, especially (but not limited to) if the documents originally were authored in previous versions of FrameMaker, is the use of what is described in the prose of the above mentioned dialog: Optimize the PDF size by running the described routines once for every file. As far as I remember you can select a book file for that feature.
HTH,
- Michael (who feels better, if he can write to people with a name)

Cross Installation

Similar Messages

Maybe you are looking for