Phaser 7750 offline

My phaser 7750 went offline some days ago and refuses to return online. I have reinstalled the driver, changed the USB cable, applied some diagnostic programmes (such as FIXIT) and all say that the printer is OK. I have tried to print from another PC, have tried a suggestion to reconfigure the printer port (however, this appeared not possible) and read an endless number of posts that could be relevant, all to no avail. However, if I press "Printerstatus" on the printer itself, it prints the status nicely and as normal. The printer identifies itself as Phaser 7750DN and I work with Windows 7. Xerox Support cannot help me because I have no maintenace contract. However, I use the printer for limited private purposes and a maintenance contract is far beyond a rational solution. As I have exhausted my imagination on what could possibly cause this problem, I post it on this forum.

Dear Joe, It is just USB.Windows does not react when I plug or unplug the printer.It displays under “printers and fax devices”It is isn’t networked but I checked the ports in the control panel of the printer as you suggested, both were enabled. What I further did today was: Open Devices and printers Xerox Phaser 7750GX PS appears as standard printer with a white V (ok) sign in green dot. Open “Printer properties”, I get choice between Xerox Phaser 7750GX PS and 7750DN PS. The GX has extra trays. I do have extra trays so I take the GX option. From the Printer Properties box I press: Print Testpage. - Nothing happens, the printer control panel says: Ready for printing. - Under: “show printing tasks”, the test page is as “Printing Error”. The title of that screen is simply: Xerox Phaser 7750GX PS. - On the “devices and printers” screen, a warning triangle appeared. - I press “solve problems” - The problem solver suggests that a document in queue (the test page) should be removed. - The problem solver says that things have been resolved and that the document in queue has been removed. - The warning sign on the Devices and printers screen disappears and the screen becomes as described under point 1. - The document in queue is still there but then disappears (but it takes very much time before that happens). I repeat exactly the steps of point 3, so I press: Print testpage - same - Under “show printing tasks”,the test page is shown as standing in queue, no error message. However, the title of the page is now: “Xerox Phaser 7750GX PS - Use printer offline”. - No warning sign on the “devices and printers” screen. - I press “solve problems”. The problems solver suggests to switch to Xerox Phaser 7750DN PS. (This doesn’t help as I know). I take the solution: Skip this solution. The solver suggest to start sharing this printer with the home group. I take the solution “skip”. - The problem solver stops without results. After these efforts, I: Installed the Mobile Express Driver from Xerox. However, once installed it does not find the Xerox Phaser 7750. When I send a test page, nothing happens and the test is not mentioned on a waiting list (it is empty).Exactly the same with the Global Printer Driver (or whateve the name is. I guess these drivers are not suitable because they expect an ethernet connection. I restored the computer to its previous state (without the installed drivers). Can this be a hardware problem after all?I don’t understand it. Greetings!, Henk van Loo

Similar Messages

Photoshop CS5: error when printing to Xerox Phaser 7750

Mac 10.6.5
I get the following error when I print directly to my Xerox Phaser 7750 from Photoshop CS5:
"Error: /Library/Printers/Xerox/Filters/pstophaserps failed"
All the other CS5 apps (plus Photoshop CS4) have no trouble printing.
Thanks in advance for any assistance.

Something doesn't add up since PS CS4 works ok. What's different about CS5? 64bit?
My guess would be that Photoshop is the only app you use that prints PostScript through the Cocoa drivers, and thus the only one hitting that particular part of the driver software.
>

CS5 on Win-7 to Xerox Phaser 7750 PS outputs 2/page printouts.

I recently upgraded to a new computer running Windows 7, 64 bit. I have the Adobe CS5 with Acrobat. When I print to my Xerox Phaser 7750 PS printer from any Adobe program (Even Reader) the output will print as if outputting 2 pages/sheet. I.E. a letter size (portrait) file will be reduced to fit on half a page, landscape orientated. If printing a multi-page document in Reader or Acrobat it will print booklet style.
I can override the problem in Reader and Acrobat by printing as an image, but the other products won't allow me to do this (or I can't figure out how!). I have the most current Xerox driver, and Xerox is telling me it is an Adobe problem since my other PS printers work fine.
I have this problem only with Adobe Programs, and only on this printer. All other programs I have print correctly to the Xerox, and the Adobe CS5 prints correctly with my other printers. The Xerox is my only Color printer and I need to fix this problem. Any help out there?

Did you ever find a solution to this problem as I have just encountered the same problem today?

Acrobat 9 and Canon iR-ADV C2030 issues

I have a user running 10.7.5 on a 2ghz MacBook Pro who constantly has issues printing PDFs to various printers. When she prints tabloid PDFs to our copier (Canon iR-ADV C2030), the prints come out fine. When she prints tabloid PDFs to any of our other printers (Xerox Phaser 7750 & 7800, HP LaserJet 5200) the prints come out the wrong size. It looks fine in the preview before she prints. I had reset her printing system, gone into the localhost settings and wiped her preferences. Only happens with PDFs, but it took a while to properly diagnose the issue (very busy user).
After much testing, this is what I've come up with: It ONLY happens with Adobe Acrobat 9, and only after printing to the Canon. The user can first print a tabloid PDF to our HP and Xerox machines with no issue. She can then print to the Canon with no ill effects. But once she prints there, it messes up the Acrobat preferences and she can no longer print tabloid correctly to any other printer but the Canon. The PDFs come out on letter at tabloid size (i.e., top corner oreinted with the rest of the image off the paper). Odd one. The problem does not occur with Acrobat X.

Based on what you have written the ADV C5035 does not have the optional Postscript (PS) kit installed. It has nothing to do with any Mavericks update.
So you will have to use the UFR2 driver you mention, which is a Canon proprietary printer language and the default printer kit in the Canon iR devices.
Note that when creating the network print queue you must use the HP Jetdirect-Socket protocol. IPP is not supported by the driver and some users have had issues with the LPD protocol.

Isolating print problems

I've been using Aperture with a Canon MP800 printer with mostly good results.
I'm an amateur photographer and right now I tend to print B&W on photo matte paper. Using the MP800's built-in presets for "colorsync profile" (and turning off color correction on the printer itself) seems to work well.
However, I've been having a lot of trouble with high contrast images, particularly the dark areas. Admittedly, I'm a novice with photography in general and digital imaging in particular, so it's hard for me to know where the problem lies. Is it my printer? Aperture? The settings? Or the image itself?
I've posted a link to a web gallery containing an example of the kind of photo I'm having trouble with. It's here
Any help or advice you could offer would be appreciated!
Chris
G5 2.0 dual-core Mac OS X (10.4.3) 17" Apple LCD, iSight, Bluetooth Keyboard & Logitech Cordless Laser Mouse

Drivers are installed both from Windows installs and from Xerox
http://www.support.xerox.com/support/phaser-7750/downloads/enus.html?operatingSystem=win7x 64&fileLanguage=sv
where Web-based Postscript Driver Installer Windows 7 64 bit is chosen.
Both these drivers have the same problem.
Windows Update didn´t solve the problem.
It´s still a mystery.

Randon printing issues (font gibberish)

Has anybody ever seen this before: You can print fine 80% of the time, but the other 20% the printout has garbled fonts. I have a user who's computer is doing just that. Every now and then, she hits print, and it comes out as gibberish - and she can immediately hit print again (without changing anything) and it comes out fine. She is the only user having this trouble, and it happens to every printer she prints too (primarily a Brother 5250 and a Xerox Phaser 7750) so I don't think it's the printer drivers. I've tried replacing all her system fonts from an identical machine, but won't know for sure yet if that's the issue. As anybody else seen this?

We have been having the same intermittent issue, although perhaps only 5% of the time or less.
It has occurred using two different laser printers (by two different manufacturers). It also is visible in on-screen previews (including FileMaker's preview mode as well as Print/ Preview), which would seem to rule out any printer hardware issue.
It has occurred with two different fonts, which were both Adobe OpenType fonts.
What we have found is that re-printing or re-previewing the document can occasionally resolve the problem, or just produce a different set of gibberish.
PowerMac G4, dual 1 GHz Mac OS X (10.4.8)

Flashpaper Print Problems..

Hi There!..
Here's the issue...
When printing from a flashpaper file that has been created
from a pdf,
there are anomalous elements that do not print correctly. The
printouts
from my machine and my colleague's machine show different
anomalies,
when printing the same file on the same printer.
One example is vertically aligned text that is white on a
coloured bg
just shows up as a white box.
Is there a definitive way to create the flashpaper from the
pdf that will
prevent this happening? Also, web links in the pdfs do not
retain their link
status, and revert to normal text, is there a way to retain
the links?
A quick look around the web has shown that many people
experience odd
printing behaviours, common comments would be...
"Apparently it depends on how the Adobe PDf document was
created or
how the FlashPaper document was produced from a PDF."
and..
"It seems that every different configuration of computer and
printer gets
a different result in how the document prints."
Anyone know of a preferred process for conversion, or suggest
a way
to modify or process the pdf prior to conversion that will
eliminate these
problems?
Cheers, JPS

Drivers are installed both from Windows installs and from Xerox
http://www.support.xerox.com/support/phaser-7750/downloads/enus.html?operatingSystem=win7x 64&fileLanguage=sv
where Web-based Postscript Driver Installer Windows 7 64 bit is chosen.
Both these drivers have the same problem.
Windows Update didn´t solve the problem.
It´s still a mystery.

COlor calibration, printing

Hi. In XP & PS 7.0.
I just got a new computer installed, same monitor tho. Ever since I got this new computer, I am unable to print in PS as well as I used to be able to a couple days ago. The color is way off. I have applied my color settings throughout all my Adobe programs to be the same in AI 10, ID CS3 & PS 7.0. I also have a Xerox Phaser 7750 GX.
There is a computer in back of me that prints great & how my computer used to print. Are there some settings that I should check there to compare with?
I have went to the color management tab under the my printer/my color printers properties & I have it as to have Windows choose the automatic color profile for both computers, but still nothing changes.
My monitor is calibrated the same way the computer in the back is, but the printout does not match what is on screen like how it used to.
I am really confused as to what other color settings to check. Please let me know if you have any info on this, I would greatly appreciate it so I can print in the Adobe programs, but mainly Photoshop!
Thank you.
Jules

Jules,
The best way to know what graphics card you have is to physically inspect it within the computer, and get exact model number info. Apart from that however, realizing you might not be able to do that conveniently, the best alternative is probably to do the following:
1. Right click on your desktop and select Properties from the menu
2. In the resulting Display Properties dialog, click the Settings tab and then the Advanced button.
3. On the next dialog that opens, select the Adapter tab. That tab will give you a description of the graphics card, although it is sometimes only giving a "family" of cards rather than the sepcific version you have. For example, the PC I'm on currently says "Radeon X1600 Series". Clicking the Properties button will open yet another dialog identifying the particular graphics drier in use.
4. On the first dialog that appears after selecting the Advanced button, you might see a tab that sometimes is added in for an ATI or nVidia card, if running one of their more complete driver installation packages. In that case, you could explore that tab for further details.
We have a Xerox Phaser 6250N in our office that I've never successfully seen any kind of high quality color output from, but then I've also never used it for anything other than generic printing tasks. If disabing ICM for a Phaser is advised as it is for my Epson R1800 when printing from Photoshop, then that is accomplished as follows:
1. Open the Printing Preferences dialog from within an application (for temporary settings) or from the specific printer's properties men in the Printers and Faxes control panel (for permanent settings).
2. On the Layout tab of the Printing Preferences, click on the Advanced button
3. In the Advance Options for the Phaser, change the "ICM Method" setting to "ICM Disabled".
I'm not really familiar with the options for a Phaser, so apart from disabling ICM, I can't advise you as to what is best. My experience is primarily with an RGB inkjet printer, and the Phaser is a CMYK printer as I understand it.
Regards,
Daryl

Printing banner images from photoshop CS3

Hi, I have successfully printed banners 1200mm x 297mm from my Xerox Phaser 7750 and Illustrator (Vector art). When I try to print a photographic image from Photoshop it all prints fine except the last 300mm or so. The image has white bars and properly printed image evenly spaced from top to bottom of the print. I have reduced the resolution and file size but the problem is still there with wider bars the lower the resolution. The original image was 160mb but I have the same issue with a 20mb image. ALso tried placing in Illustrator but get similar problems.
I assume this is a memory issue but I thought lowering the file size drastically would fix it, yet it doesn't. The Printer has a relatively low amount of memory (384mb) but I would like to know if this is the real cause before I dive and buy more memory - big chips are still expensive on this.
Any help would be very welcome.
Thanks. Ant

Hi, I will try printing from inDesign but I have managed to get an image to print out by changing the quality in the print driver to standard - it was previously on 'Enhanced' or 'Photo'. I had tried from Illustrator and had similar problems (printed OK with Illy created art though) so thought it may be a printer memory issue which does seem to be the case. I assumed that by reducing the file size/resolution it would print but it seemed to be the image quality that uses more computing power than the pixel count of the file. I guess a different RIP may also help as it could use the much higher RAM of the Mac rather than the printers meagre 384mb.
I had originally thought it may be a P/Shop issue as I had problems printing to Epson inkjet some months ago and then Epson and Adobe seemed to blame each other!
Thanks for the reply.

Print Preview doesn't reflect what is chosen from my printer properties

I recently reinstalled my Windows XP Pro machine, installed Photoshop CS4 (actually Master Collection CS4) and installed the latest printer driver from Xerox for my Xerox Phaser 7750 printer. I had a project to print out and it was 12x18. I chose the paper size in my printer properties, but the print preview in Photoshop CS4 would not reflect it, it would continue to say 8 1/2" x 11", even though it showed 12 x 18 in the scaled Print Size box. When I print it accepted the 12x18 and chose the right tray to pull the paper from, but it only printed the 8 1/2" x 11" and cut everything else off.
What could possibly be going on here? It used to work fine on my Photoshop CS2. Is it the latest driver causing an issue? The crazy thing is that I saved my project as a PDF and printed from PDF just fine, so it seems like Photoshop is having some issue.
Any help would be appreciated.

I feel a little silly right about now. I came home, brought up Photoshop and everything worked as it should. I don't know why it didn't before, except that maybe I installed Photoshop, started it and realized I didn't have the printer installed yet, then I installed the printer driver and didn't restart photoshop. If that was the case I could see why I would have problems. Thank you so much for your suggestions though, people that are willing to help even when it is the fault of the user are amazing. Thanks so much!

The problem is this: In the phase "Create Java Users"

Hello,
I am installing Solution Manager 4.0 Release 2 (with Red Hat Enterprise Linux Server release 5.1 and Oracle 10 and my java version is: j2sdk1.4.2_14) The problem is this: In the phase "Create Java Users" I get the next error
WARNING 2009-02-13 14:53:22
Execution of the command "/usr/sap/PTS/DVEBMGS00/exe/jlaunch UserCheck.jlaunch com.sap.security.tools.UserCheck /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install -c sysnr=00 -c ashost=sap-vpmn -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message" finished with return code 2. Output:
java.lang.ClassNotFoundException: com.sap.security.tools.UserCheck
at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
INFO 2009-02-13 14:53:22
Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.
INFO 2009-02-13 14:53:22
Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.clone.
ERROR 2009-02-13 14:53:22
CJS-30196
ERROR 2009-02-13 14:53:22
FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with status ERROR .
Thanks & Regards

Hi,
This problem normally arises with the wrong combination of JDK and OS and for the Linux machines, its better to use IBM Java instead of SUN java
I remember that I have solved this type of problem by using lower version of IBMJava2-AMD64-142-SDK-1.4.2-10.0.x86_64.rpm which is SR10. You can download this version from
http://www.ibm.com/developerworks/java/jdk/linux/download.html
go to download _12 and then just change the sr12 to sr10 in the header url....
FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with status ERROR .
with the higher versions of java for 64bit systems create serious stack over flow problems.....
what I suggest you is to start reinstallating SolMan after installing IBM java sr10 version...
Regards,
Naveen.

SAP NetWeaver 7.3 AS Java install error in Install Java Engine phase

Hi All,
I am doing my first installation of SAP NetWeaver 7.3 AS Java on Windows Server 2008 R2 with Oracle database 11.2.0.3, this is a domain installation.
I have been following the SAP Installation guide and everything has been going well but I am now stuck with an error in the Install Java Engine phase of the installation.
The error message I am receiving is:
An error occurred while processing option SAP NetWeaver 7.3 > SAP Systems > Application Server Java > Standard System > Standard System( Last error reported by the step: Process call 'C:\usr\sap\E1D\J00\exe\jstart.exe pf=\\sourcing\sapmnt\E1D\SYS\profile\E1D_J00_sourcing -file=C:\usr\sap\E1D\J00\exe\startup.properties -nodename=bootstrap -launch' exits with error code 1. For details see log file(s) jstart_bootstrap_J00.log.)
When I check the jstart_bootstrap_J00.log it is empty.
I have done some searching for a solution for this error and it seems it may be related to the database not running. I can confirm that I have run lsnrctl start and also, in sqlplus, run startup; both commands showed that the starting of the listener and database were successful.
Does anyone know what might be causing this error?
Many thanks
Dan

Hi Srikishan,
In C:\Program Files\sapinst_instdir\NW73\INSTALL\NW73\ORA\STD the file jstart_bootstrap_J00.log is empty.
In C:\usr\sap\E1D\J00\work there was no jstart_bootstrap_J00.log file, however there was a file called log_bootstrap.0.log, the contents are:











[Aug 22, 2012 12:11:10 PM] Starting to configure the bootstrap
[Aug 22, 2012 12:11:10 PM]       Bootstrap properties file [C:\usr\sap\E1D\J00\j2ee\cluster\bootstrap\bootstrap.properties] found
[Aug 22, 2012 12:11:10 PM] Bootstrap configured for [32] ms
[Aug 22, 2012 12:11:10 PM]
[Aug 22, 2012 12:11:10 PM] Memory available to the bootstrap JVM: [2 GiB / 3113877504 bytes]
[Aug 22, 2012 12:11:10 PM]
-----[Bootstrap Module started]--------[Wed Aug 22 12:11:10 BST 2012]-------
[Aug 22, 2012 12:11:10 PM]
+------------[Bootstrap synchronization activities information]-----------+
| Runtime Binaries: [X]        Native files: [X] Instance Properties: [X] |
| Nodes Structure: [X] Cluster File System: [X]    Online bootstrap: [ ] |
+-------------------------------------------------------------------------+
[Aug 22, 2012 12:11:10 PM] Properties used for initialization: [element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, log[defaultTrace].pattern=..\..\work\log_bootstrap.log, log[consoleLog].formatter=formatter[ConsoleFormatter], com.sap.engine.bootstrap.severity=Info, formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, com.sap.engine.bootstrap.logs=log[defaultTrace],log[consoleLog], log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, formatter[BootstrapFormatter].pattern=[%24d] %m}, debug=no, Watchdog properties = {watchdog.timeout=90000, watchdog.check_interval=2000}]
[Aug 22, 2012 12:11:10 PM] Bootstrap initialized for [63] ms
[Aug 22, 2012 12:11:10 PM] Watchdog [90000] ms checking every [2000] ms started
[Aug 22, 2012 12:11:10 PM] Starting to initialize database connection
[Aug 22, 2012 12:11:11 PM] Exception occurred for component [internal/unkown] of type [unkown]
com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed.Check if the database is running and the database connection properties
    at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:138)
    at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:412)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:167)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)
    at com.sap.engine.core.configuration.impl.cache.ConfigurationController.<init>(ConfigurationController.java:138)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:307)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
    at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:131)
    at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class oracle.jdbc.driver.OracleDriver with class loader com.sap.engine.offline.FileClassLoader@68814013.
    at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)
    at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:210)
    at com.sap.sql.connect.factory.VendorConnectionFactory.createVendorDriver(VendorConnectionFactory.java:43)
    at com.sap.sql.connect.factory.DriverPooledConnectionFactory.<init>(DriverPooledConnectionFactory.java:31)
    at com.sap.sql.connect.datasource.DataSourceManager.createPooledConnectionFactory(DataSourceManager.java:642)
    at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:603)
    at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:137)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.getDataSource(OpenSQLDataSourceImpl.java:272)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:208)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:399)
    ... 13 more
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
    at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:911)
    at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:802)
    at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:750)
    at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:206)
    ... 21 more
[Aug 22, 2012 12:11:11 PM] [Bootstrap]> Error during synchronization. More details: the previous log entries
[Aug 22, 2012 12:12:29 PM] Starting to configure the bootstrap
[Aug 22, 2012 12:12:29 PM]       Bootstrap properties file [C:\usr\sap\E1D\J00\j2ee\cluster\bootstrap\bootstrap.properties] found
[Aug 22, 2012 12:12:29 PM] Bootstrap configured for [32] ms
[Aug 22, 2012 12:12:29 PM]
[Aug 22, 2012 12:12:29 PM] Memory available to the bootstrap JVM: [2 GiB / 3113877504 bytes]
[Aug 22, 2012 12:12:29 PM]
-----[Bootstrap Module started]--------[Wed Aug 22 12:12:29 BST 2012]-------
[Aug 22, 2012 12:12:29 PM]
+------------[Bootstrap synchronization activities information]-----------+
| Runtime Binaries: [X]        Native files: [X] Instance Properties: [X] |
| Nodes Structure: [X] Cluster File System: [X]    Online bootstrap: [ ] |
+-------------------------------------------------------------------------+
[Aug 22, 2012 12:12:29 PM] Properties used for initialization: [element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, log[defaultTrace].pattern=..\..\work\log_bootstrap.log, log[consoleLog].formatter=formatter[ConsoleFormatter], com.sap.engine.bootstrap.severity=Info, formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, com.sap.engine.bootstrap.logs=log[defaultTrace],log[consoleLog], log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, formatter[BootstrapFormatter].pattern=[%24d] %m}, debug=no, Watchdog properties = {watchdog.timeout=90000, watchdog.check_interval=2000}]
[Aug 22, 2012 12:12:29 PM] Bootstrap initialized for [63] ms
[Aug 22, 2012 12:12:29 PM] Watchdog [90000] ms checking every [2000] ms started
[Aug 22, 2012 12:12:29 PM] Starting to initialize database connection
[Aug 22, 2012 12:12:30 PM] Exception occurred for component [internal/unkown] of type [unkown]
com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed.Check if the database is running and the database connection properties
    at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:138)
    at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:412)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:167)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)
    at com.sap.engine.core.configuration.impl.cache.ConfigurationController.<init>(ConfigurationController.java:138)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:307)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:57)
    at com.sap.engine.bootstrap.StorageAccess.<init>(StorageAccess.java:131)
    at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:79)
    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:273)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:157)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class oracle.jdbc.driver.OracleDriver with class loader com.sap.engine.offline.FileClassLoader@38ee6681.
    at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)
    at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:210)
    at com.sap.sql.connect.factory.VendorConnectionFactory.createVendorDriver(VendorConnectionFactory.java:43)
    at com.sap.sql.connect.factory.DriverPooledConnectionFactory.<init>(DriverPooledConnectionFactory.java:31)
    at com.sap.sql.connect.datasource.DataSourceManager.createPooledConnectionFactory(DataSourceManager.java:642)
    at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:603)
    at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:137)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.getDataSource(OpenSQLDataSourceImpl.java:272)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:208)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:399)
    ... 13 more
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
    at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:911)
    at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:802)
    at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:750)
    at com.sap.sql.connect.factory.VendorConnectionFactory.createInstance(VendorConnectionFactory.java:206)
    ... 21 more
[Aug 22, 2012 12:12:30 PM] [Bootstrap]> Error during synchronization. More details: the previous log entries
Many thanks
Dan

Error in Import Java Dump phase

Hi
I am trying to install netweaver 2004s on windows 2003 server with MSSQL as the database
All the installation steps went fine until the IMPORT JAVADUMP PHASE.
The error says "cannot connect to the DB" in this phase.
Please help me in this regard ASAP. Below is the error.
INFO 2009-03-31 17:50:31
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\MSS\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx512m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/jload.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/antlr.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/exception.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/jddi.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/logging.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/offlineconfiguration.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/opensqlsta.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/base.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/util.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/sqlserver.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/spy.jar" -sec EP1,jdbc/pool/EP1,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.properties,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.key -dataDir "D:/nw dump/javacomp\JAVA_EXPORT\JDMP" -job "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML" -log jload.log is written to the logfile C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/jload.java.log.
WARNING 2009-03-31 17:50:47
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\MSS\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx512m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/jload.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/antlr.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/exception.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/jddi.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/logging.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/offlineconfiguration.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/opensqlsta.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/base.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/util.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/sqlserver.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/spy.jar" -sec EP1,jdbc/pool/EP1,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.properties,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.key -dataDir "D:/nw dump/javacomp\JAVA_EXPORT\JDMP" -job "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML" -log jload.log" finished with return code 1. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
31-Mar-2009 17:50:32 com.sap.inst.jload.Jload main
INFO: Jload -sec EP1,jdbc/pool/EP1,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.properties,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.key -dataDir D:/nw dump/javacomp\JAVA_EXPORT\JDMP -job C:\Program Files\sapinst_instdir\NW04S\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML -log jload.log
31-Mar-2009 17:50:47 com.sap.inst.jload.Jload main
SEVERE: couldn't connect to DB
31-Mar-2009 17:50:47 com.sap.inst.jload.Jload logStackTrace
SEVERE: java.sql.SQLException: [NWMss][SQLServer JDBC Driver][NWMss][SQLServer JDBC Driver]The requested instance is either invalid or not running.
     at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
     at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source)
     at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
     at com.sap.inst.jload.db.DBConnection.connectViaSecureStore(DBConnection.java:105)
     at com.sap.inst.jload.db.DBConnection.connect(DBConnection.java:149)
     at com.sap.inst.jload.Jload.main(Jload.java:580)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
ERROR 2009-03-31 17:50:47
CJS-30049 <html>Execution of JLoad tool 'C:\j2sdk1.4.2_12\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\MSS\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx512m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/jload.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/antlr.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/exception.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/jddi.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/logging.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/offlineconfiguration.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/opensqlsta.jar;C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/base.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/util.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/sqlserver.jar;D:/usr/sap/EP1/SYS/exe/uc/NTI386/mssjdbc/spy.jar" -sec EP1,jdbc/pool/EP1,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.properties,
dixie/sapmnt/EP1/SYS/global/security/data/SecStore.key -dataDir "D:/nw dump/javacomp\JAVA_EXPORT\JDMP" -job "C:\Program Files\sapinst_instdir\NW04S\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML" -log jload.log' aborts with return code 1.<br>SOLUTION: Check 'jload.log' and 'C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/jload.java.log' for more information.</html>
ERROR 2009-03-31 17:50:47
FCO-00011 The step importJavaDump with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Jload|ind|ind|ind|ind|9|0|importJavaDump was executed with status ERROR .

Hi,
The above error says
SOLUTION: Check 'jload.log' and 'C:/Program Files/sapinst_instdir/NW04S/SYSTEM/MSS/CENTRAL/AS/jload.java.log' for more information.
Have a look @ the post in the below section
Expert Forums » SAP NetWeaver » SAP NetWeaver Administrator
Thread: Error - installing Net Weaver 2004s SR2
Can you please post the jload.java.log here
Let us know if you have any issues,
Regards,
Ravi

Problem with the UPGRADE in the PHASE - DEPLOY_ONLINE

Hello Expert,
I have a problem when a try to execute the upgrade in the phase
DEPLOY_ONLINE,
<<<<<<<<<<<BEGIN TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>
Trouble Ticket Report
Upgrade to SAP NetWeaver'04s
SID................: J2E
Hostname...........: sapepd
Install directory..: d:/usr/sap/J2E
Upgrade directory..: D:\SAPEPD\saploc\jupgrade
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.4.2_11 Sun Microsystems Inc.
SAPJup version.....: 1.1.101
Source release.....: 630
Target release.....: 700
Current usages.....: EP;AS;DI
ABAP stack present.: false
The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
Cannot execute Java process for deployList with parameters
D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.
Return code condition success evaluated to false for process java.exe
for action ACTION_DEPLOY_LIST.
More information can be found in the log file
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
Use the information provided to trouble-shoot the problem. There might
be an OSS note providing a solution to this problem. Search for OSS
notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
com.sap.sdt.ucp.phases.PhaseException
Error while executing SDM process phase with action DEPLOY_SLOT. See
D:\SAPEPD\saploc\jupgrade\log\DEPLOY_SLOT_0__DON_01.LOG for details.
DEPLOY_ONLINE
UPGRADE
NetWeaver Upgrade
SAPJup
Java Upgrade
<<<<<<<<<<< END OF TROUBLE TICKET >>>>>>>>>>>>>>>>>>>>>>>>>
THE FILE: DEPLOY_ONLINE_DON_01.LOG
BEGIN DEPLOY_ONLINE_DON_01.LOG----
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\SAPEPD\saploc\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG]/>
<!PATTERN[DEPLOY_ONLINE_DON_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC10C807000000000B1D010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B1E010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess#
#1.5#C000AC10C807000000000B1F010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#action#DEPLOY_SLOT#
#1.5#C000AC10C807000000000B20010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#connect#standard#
#1.5#C000AC10C807000000000B21010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:755)#Java###Checking phase parameters .#1#action, connect#
#1.5#C000AC10C807000000000B22010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.checkParameters(PhaseTypeSDMProcess.java:764)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#1#
#1.5#C000AC10C807000000000B23010BC49D0004358E71467A38#1184785808915#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.createSlotDeployLists(PhaseTypeSDMProcess.java:1216)#Java###Temporary file has been created.#1#D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.LST#
#1.5#C000AC10C807000000000B24010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:46)#Java###Java process ID has been started.#1#249#
#1.5#C000AC10C807000000000B25010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #C:
j2sdk
jre
bin
java.exe -Xmx256M -Djava.ext.dir=d:/usr/sap/J2E/JC00/SDM/program/lib -cp . -jar d:
usr
sap
J2E
JC00
SDM
program
bin
SDM.jar deploy onerror=skipdepending updateversions=all list=D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST sdmHome=d:/usr/sap/J2E/JC00/SDM/program logfile=D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG#
#1.5#C000AC10C807000000000B26010BC49D0004358E7146B8B8#1184785808931#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.OUT#
#1.5#C000AC10C807000000000B27010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#249#
#1.5#C000AC10C807000000000B28010BC49D0004358E7146F350#1184785808946#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#249#java.exe#
#1.5#C000AC10C807000000000B29010BC49D0004358E90915390#1184786333914#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#249#java.exe#4#
#1.5#C000AC10C807000000000B2A010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC10C807000000000B2B010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:513)#Java###Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.##
#1.5#C000AC10C807000000000B2C010BC49D0004358E90918E28#1184786333929#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.sdmprocess.AbstractSDMProcessCall.deployList(AbstractSDMProcessCall.java:722)#Java###Cannot execute Java process for deployList with parameters D:/SAPEPD/saploc/jupgrade/tmp/SLOT.DEPLOY.PRE.01.LST.##
#1.5#C000AC10C807000000000B2D010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess.execute(PhaseTypeSDMProcess.java:735)#Java###Error while executing SDM process phase with action DEPLOY_SLOT. See D:
SAPEPD
saploc
jupgrade
log
DEPLOY_SLOT_0__DON_01.LOG for details.##
#1.5#C000AC10C807000000000B2E010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#UPGRADE/UPGRADE/DEPLOY_ONLINE#
#1.5#C000AC10C807000000000B2F010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/18 15:10:08#
#1.5#C000AC10C807000000000B30010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/18 15:18:53#
#1.5#C000AC10C807000000000B31010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:08:45.030#
#1.5#C000AC10C807000000000B32010BC49D0004358E9091CCA8#1184786333945#/System/Server/Upgrade/Phases/UPGRADE/UPGRADE/DEPLOY_ONLINE##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
*************END DEPLOY_ONLINE_DON_01.LOG*******************
FILE ************** DEPLOY_SLOT_0__DON_01.LOG
BEGIN DEPLOY_SLOT_0__DON_01.LOG----
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:33 PM Info: Starting to save the repository
Jul 18, 2007 3:18:33 PM Info: Finished saving the repository
Jul 18, 2007 3:18:33 PM Info: Starting: Initial deployment: Selected development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' will be deployed.
Jul 18, 2007 3:18:33 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\samples\testsuite\uuie\SAP AG\0\7.0010.20061002110342.0000\TestSuiteUUIE.sda
Jul 18, 2007 3:18:33 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:33 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Info: Begin of log messages of the target system:
07/07/18 15:18:33 - ***********************************************************
07/07/18 15:18:34 - Start updating EAR file...
07/07/18 15:18:34 - start-up mode is lazy
07/07/18 15:18:34 - EAR file updated successfully for 172ms.
07/07/18 15:18:34 - Start deploying ...
07/07/18 15:18:34 - EAR file uploaded to server for 500ms.
07/07/18 15:18:36 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
                     Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
                          com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                          at java.security.AccessController.doPrivileged(Native Method)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                     Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
                          at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
                          ... 10 more
                     For detailed information see the log file of the Deploy Service.
07/07/18 15:18:36 - ***********************************************************
Jul 18, 2007 3:18:36 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:36 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:36 PM Error: Aborted: development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/tcwdsamplestestsuiteuuie..
Reason: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/tcwdsamplestestsuiteuuie. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jul 18, 2007 3:18:36 PM Info: Starting to save the repository
Jul 18, 2007 3:18:36 PM Info: Finished saving the repository
Jul 18, 2007 3:18:36 PM Info: Starting: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112146.0000'/'0'.
Jul 18, 2007 3:18:36 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\tools\SAP AG\0\7.0011.20061227101805.0000\WebDynproTools.sda
Jul 18, 2007 3:18:36 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:36 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Begin of log messages of the target system:
07/07/18 15:18:36 - ***********************************************************
07/07/18 15:18:36 - Start updating EAR file...
07/07/18 15:18:36 - start-up mode is lazy
07/07/18 15:18:37 - EAR file updated successfully for 375ms.
07/07/18 15:18:37 - Start updating...
07/07/18 15:18:37 - EAR file uploaded to server for 422ms.
07/07/18 15:18:39 - Successfully updated. Update took 1641ms.
07/07/18 15:18:39 - Deploy Service status:
07/07/18 15:18:39 -    Application : sap.com/tcwdtools
07/07/18 15:18:39 -
07/07/18 15:18:39 -    sap.com/tcwdtools - WEBDYNPRO
07/07/18 15:18:39 -    sap.com/tcwdtools monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:39 - ***********************************************************
Jul 18, 2007 3:18:39 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:39 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:39 PM Info: Finished successfully: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'7.0011.20061227101805.0000'/'0', grouped by :
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:39 PM Info: Starting to save the repository
Jul 18, 2007 3:18:40 PM Info: Finished saving the repository
Jul 18, 2007 3:18:40 PM Info: Starting: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4020.00.0000.20070308112008.0000'/'0'.
Jul 18, 2007 3:18:40 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda
Jul 18, 2007 3:18:40 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:40 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Begin of log messages of the target system:
07/07/18 15:18:40 - ***********************************************************
07/07/18 15:18:40 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda...
07/07/18 15:18:40 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\wslib\SAP AG\0\7.0011.20070125102926.0000\WebDynproWsLib.sda successfully deployed on the server.
Jul 18, 2007 3:18:40 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:40 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:40 PM Info: Finished successfully: development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'7.0011.20070125102926.0000'/'0', grouped by
Jul 18, 2007 3:18:40 PM Info: Starting to save the repository
Jul 18, 2007 3:18:41 PM Info: Finished saving the repository
Jul 18, 2007 3:18:41 PM Info: Starting: Initial deployment: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0' will be deployed.
Jul 18, 2007 3:18:41 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\workflowmodeler\SAP AG\0\7.0011.20050509144048.0000\Modeler.sda
Jul 18, 2007 3:18:41 PM Info: Software type of SDA: J2EE
Jul 18, 2007 3:18:41 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:41 - ***********************************************************
07/07/18 15:18:41 - Start updating EAR file...
07/07/18 15:18:41 - start-up mode is lazy
07/07/18 15:18:42 - EAR file updated successfully for 1000ms.
07/07/18 15:18:42 - Start deploying ...
07/07/18 15:18:43 - EAR file uploaded to server for 891ms.
07/07/18 15:18:48 - Successfully deployed. Deployment took 5375ms.
07/07/18 15:18:48 -    Application : sap.com/tc~workflowmodeler
07/07/18 15:18:48 -
07/07/18 15:18:48 -    /Application/WorkflowModeler - LOGGING CONFIGURATION
07/07/18 15:18:48 -    com.sap.workflowmodeler.modeler - LOGGING CONFIGURATION
07/07/18 15:18:48 -    workflowBean - EJB
07/07/18 15:18:48 -    WorkflowConnection - EJB
07/07/18 15:18:48 -    Modeler - WEB
07/07/18 15:18:48 -    sap.com/tc~workflowmodeler monitoring configuration - MONITORING CONFIGURATION
07/07/18 15:18:48 - ***********************************************************
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 18, 2007 3:18:49 PM Info: Finished successfully: development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'7.0011.20050509144048.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
The application start is forbidden, because of the server mode and action.
Jul 18, 2007 3:18:49 PM Info: Starting to save the repository
Jul 18, 2007 3:18:49 PM Info: Finished saving the repository
Jul 18, 2007 3:18:49 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:49 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda
Jul 18, 2007 3:18:49 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:49 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:49 PM Info: Begin of log messages of the target system:
07/07/18 15:18:49 - ***********************************************************
07/07/18 15:18:49 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda...
07/07/18 15:18:49 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Client\SAP AG\0\7.0011.20061227100346.0000\SDMClient.sda successfully deployed on the server.
Jul 18, 2007 3:18:49 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:49 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Client'/'sap.com'/'SAP AG'/'7.0011.20061227100346.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:50 PM Info: Finished saving the repository
Jul 18, 2007 3:18:50 PM Info: Starting: Update: Selected development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0' updates currently deployed development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'6.4014.00.0000.20050818153711.0000'/'0'.
Jul 18, 2007 3:18:50 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda
Jul 18, 2007 3:18:50 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:50 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Begin of log messages of the target system:
07/07/18 15:18:50 - ***********************************************************
07/07/18 15:18:50 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda...
07/07/18 15:18:50 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc_SL_SDM_Util\SAP AG\0\7.0010.20061019070020.0000\SDMutil.sda successfully deployed on the server.
Jul 18, 2007 3:18:50 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:50 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:50 PM Info: Finished successfully: development component 'tc_SL_SDM_Util'/'sap.com'/'SAP AG'/'7.0010.20061019070020.0000'/'0', grouped by
Jul 18, 2007 3:18:50 PM Info: Starting to save the repository
Jul 18, 2007 3:18:51 PM Info: Finished saving the repository
Jul 18, 2007 3:18:51 PM Info: Starting: Initial deployment: Selected development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0' will be deployed.
Jul 18, 2007 3:18:51 PM Info: SDA to be deployed: D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda
Jul 18, 2007 3:18:51 PM Info: Software type of SDA: library
Jul 18, 2007 3:18:51 PM Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Begin of log messages of the target system:
07/07/18 15:18:51 - ***********************************************************
07/07/18 15:18:51 - Start deploying library JAR D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda...
07/07/18 15:18:52 - Library D:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\sdt\cvl\SAP AG\0\7.0010.20060210160258.0000\sap.comtcsdt~cvl.sda successfully deployed on the server.
Jul 18, 2007 3:18:52 PM Info: End of log messages of the target system.
Jul 18, 2007 3:18:52 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Jul 18, 2007 3:18:52 PM Info: Finished successfully: development component 'tc/sdt/cvl'/'sap.com'/'SAP AG'/'7.0010.20060210160258.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0'
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0' will be deployed.
Jul 18, 2007 3:18:52 PM Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.7.00.11.0.20070201154800''/'0':
Failed deployment of SDAs:
development component 'tc/wd/samples/testsuite/uuie'/'sap.com'/'SAP AG'/'7.0010.20061002110342.0000'/'0' : aborted
Please, look at error logs above for more information!
Jul 18, 2007 3:18:52 PM Info: Starting to save the repository
Jul 18, 2007 3:18:52 PM Info: Finished saving the repository
Jul 18, 2007 3:18:52 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jul 18, 2007 3:18:52 PM Error: -
At least one of the Deployments failed -
Jul 18, 2007 3:18:53 PM Info: Summarizing the deployment results:
Jul 18, 2007 3:18:53 PM Info: OK: D:\SAPEPD\saploc\jupgrade\data\archives\EPBC11_0-10003473.SCA
Jul 18, 2007 3:18:53 PM Error: Aborted: D:\SAPEPD\saploc\jupgrade\data\archives\SAPJTECHS11_0-10003467.SCA
Jul 18, 2007 3:18:53 PM Error: Processing error. Return code: 4
END DEPLOY_SLOT_0__DON_01.LOG----
I SAW the SDN forum and talk about the question
Nw2004s Upgrade: Error in phase DEPLOY_ONLINE
but this one doesnu00B4t work
best regards
Luis Moreno

Hi
I resolved the issue by undeploying the TestSuiteUUIE component using SDM.
Thanks
Naresh P.

Error during java migration tool kit phase

Hi All ,
We are migrating the BI 7.00 EHP1 from (Win 2008/SQL 2008) to Target (Win 2008/SQL 2008).This is a export/Import based method using sapinst tool.
Import stopped at the "Java Migration Toolkit" phase.The following are the error logs , if anybody faced same issue please help with your inputs.
runJmt.log
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:282)
at com.sap.sdt.jmt.migrationtool.ConfigurationHandlerFactoryManager.getConfigurationHandlerFactory(ConfigurationHandlerFactoryManager.java:63)
at com.sap.sdt.jmt.migrationtool.MigrationToolUtils.getSourceConfigurationFactory(MigrationToolUtils.java:178)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:260)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
... 13 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The port number error_con is not valid.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)
... 18 more
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:282)
at com.sap.sdt.jmt.migrationtool.ConfigurationHandlerFactoryManager.getConfigurationHandlerFactory(ConfigurationHandlerFactoryManager.java:63)
at com.sap.sdt.jmt.migrationtool.MigrationToolUtils.getTargetConfigurationFactory(MigrationToolUtils.java:190)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:262)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
... 13 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The port number error_con is not valid.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)
... 18 more
Could not initialize the offline configuration managers.

Hi,
First check you port numbers as per error, that port is not use.
The port number error_con is not valid.
Also check this sap note
1788188 - Couldn't connect to DB during java install
Then also check this link with same problem, suggestion is replacing the default kernel from DVD with later one.
http://scn.sap.com/thread/1203147
KInd Regards,
Johan

Phaser 7750 offline

Similar Messages

Maybe you are looking for