Copy client manually with TP-commando

Hi!
I am about to delete and then to import a client from productive client into the QAS-system.
I perform the deletion of the client not via SCC5, but with skript that executes the following:
clientremove
client=300
select *
The files from client-export were generated into the \cofiles and \data
Now I would like to execute the import manually with tp import commando.
Question
What ais the right TP commando for this import?
tp pf=TPPARAM import "<sid>KT12345" <sid> clientxxx u148 "-Dr3transoptions=tcs=160000 commit=128000"
What are especially the right u-code, tcs and commit values?
Thank you

Why not use a computer startup script where you specify the path to the installation files. Check the script from Jason, it allows you to control the entire procss -
http://blogs.catapultsystems.com/jsandys/archive/2010/12/30/updated-configmgr-startup-script.aspx
Kent Agerlund | My blogs: blog.coretech.dk/keaand
SCUG.dk/| Twitter:
@Agerlund| Linkedin: Kent Agerlund
Script looks interesting, thanks Kent. Though there wouldn't be enough time to implement for these few PC's. If they just run copy down the 'Client' folder and then run CCMSETUP.exe locally without switches, would this be enough? Then later
on the newly installed client will retrieve settings from AD?

Similar Messages

Was I supposed to get a hard copy user manual with my new phone??

Was I supposed to get a hard copy user manual with my new phone??
I did not get one - but would like one

http://manuals.info.apple.com/enUS/iPhone_UserGuide.pdf
There you go!
Enjoy

Copy client with open items FI, stocks MM and balance from one client to

Hi Gurus,
I have a question , I want to copy client with next information:
1.- All Cuztomazing
2.- All master data
3.- Only open items FI-AR , FI-AP,
4.- Stocks MM available for production.
5.- Documents sales valids
6.- Complete Balance (fixed , available and current asset, etc.)
From one client to other client.
¿How can I do it?
I know that cuztomazing and master data it's possible, I need to find from 3 to 6 point if it's possible for copy tables or some trx complete this information.
This work it's because my company code changue NIF and information TAX , and I need to have a cut over for carry forward only the describe information.
Thank's a lot
Regards
Julio

Hi Julio,
How did you solve this? I need to perform exactly these steps.
I am very interested in 3, 4 and 6.
Thanks in advance.

Copy client with open items FI, stocks and balance

Hi Gurus,
I have a question , I want to copy client with next information:
1.- All Cuztomazing
2.- All master data
3.- Only open items FI-AR , FI-AP,
4.- Stocks MM available for production.
5.- Documents sales valids
6.- Complete Balance (fixed , available and current asset, etc.)
From one client to other client.
¿How can I do it?
I know that cuztomazing and master data it's possible, I need to find from 3 to 6 point if it's possible for copy tables or some trx complete this information.
This work it's because my company code changue NIF and information TAX , and I need to have a cut over for carry forward only the describe information.
Thank's a lot
Regards
Julio

Hi Julio,
How did you solve this? I need to perform exactly these steps.
I am very interested in 3, 4 and 6.
Thanks in advance.

Loging on new client copying from 0000 with SCC4 is failure(ECC6)

Hi,Expers:
Now I have a quesion: After I finished the ECC 6 Installation, I want to copy a new client.
So I log on the client: 000 with name: SAP*, and finished copying a new client :100 with tcode: SCC4.
Then I log off the SAP system and restart the SAP MMC and OS.After that, I log on the SAP client:100 with name :SAP*.
but, I can't log in the new client:100 ,system shows error messages: Name or password is in correct (repeat logon).
Have logon Name: SAP* any issues: password or the other reasons?
Have anyone the question??
Plesase help me solve the issue, Thanks in advance

Hi Lin,
After new installation we have to changed setting in instance file for use sap* user in new client.
First you import the profile.
The user name SAP* is only active if the profile parameter login/no_automatic_user_sapstar does not have the value 1.
Regards,
Anil

How to make copy client with customizing but with no deleting appl.data

Hello,
Which profile of copy client i need if i want make copy customizing without deleting application data in target client.
regards,
Denis

hello dennis,
There is no way you can do that, you cannot copy only customizing onto a client without deleting the application data since there is no such profile in the client copy profiles to do so.
Also, to me it seems a bit strange to keep the application data (which depends on customizing for integrity) and update the customizing with something else!
However, still if you wish to do this, there is a crude way of doing it (theoratically). You could use the client copy by a transport request where in you club all your customizing transport requests into one single transport request using transport of copies and then use the client copy via transport request to copy the customizing.
Here are the steps:
1. Create transport of copies [click here|http://help.sap.com/saphelp_nw70/helpdata/EN/57/38e1a94eb711d182bf0000e829fbfe/frameset.htm]
2. Copy the newly created transport request into the target client via copy by a transport request functionality.
click the following link for the same:
[client copy via transport request|http://help.sap.com/saphelp_nw70/helpdata/EN/69/c24c754ba111d189750000e8322d00/frameset.htm]
Regards,
Siddhesh

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

ICal (Client) version with 10.6.2, intermittently loses "Refresh Frequency"

iCal (Client) version with 10.6.2, intermittently loses "Refresh Frequency"
10.6.2 SLS with 1.5 mo. new MacPro tower with 4 Cores (just bought)
3GB RAM
Network Homes
Network Calendars (only, no published things, no busysync, all Apple Champagne)
iCal Server enable
Solid, fast network homes, logins quick, kick-*** OD implementation, very few beach balls, though they grow when I get all 12 delegates refreshing calendars every minute.
Push turned off (it doesn't work as advertised, in my tests)
Set iCal client to refresh each minute
12 Read/Write Delegates for each of 13 workstations. (so, we're really expecting a lot, but not a lot, like in, we expect Exchange/Outlook robustness -- on open standards woo hoo)
But yeah, the main symptom is that the ical client loses it mind (at some as yet undetermined interval) and stops refreshing. And the formerly trusting Calendar user, misses a meeting, because the change the delegate made to their calender didn't refresh and the Calendar user shows up an hour late, or misses the event entirely. That won't work.
OK. back to what I've tried. (I haven't tried, but am considering it, moving to PHD)
I have turned off PUSH. I hope that returns some server processing cycles.
I have ( and this fixes it temporarily ) set their refresh frequency to manual. Close Prefs. Open Prefs, set back to 1 Minute. Close prefs. And that holds for a day (?) two days (?) I haven't gotten that far yet. I did that last night. And it saved me from having to remove and add the network calendar account. So, my remedy is down to about 40 seconds and 10 mouse clicks. Still annoying, and should work properly.
Apple Enterprise support is being awesome. They send me the engineering capture tool and I am awaiting the symptom return. Then I run that app and it gobbles up lots of logs on an affected client workstation and the server. So, wish me luck, and send any thoughts or ideas along.

This looks like a bug in the iCal client. I, too, have had problems with delegated calendars and end users mistaking events for being missing, not updated or incorrect only because their local copy was not synced with the true copy on the server. The refresh rate on delegated calendars can be changed with the "Refresh calendars: [ Every 1 minute ]" preference. You can verify this by right-clicking or control-clicking on the delegated calendar and choosing "Show CalDAV Queue." This brings up a queue of activity with the iCal Server. You'll note at the top that it mentions "Refresh every 1 minute."
The problem, of course, is if you quit iCal and recheck the "Show CalDAV Queue" on the delegated calendar, the refresh interval has reverted to some long interval like 300 or 900 minutes. This is a bug, for sure. For now, you can tell your clients not to quit iCal or to refresh manually or reset the refresh interval whenever they restart iCal/their computer, etc.

I can no longer copy files manually to our external drive?

Hi - I'm not sure what happened here, and I'm hoping someone can help. Basically, we are starting to film library programs for local TV. A colleague at the high school with a lot of experience was kind enough to buy us a mybook external drive (one terabyte!) to store our video and audio files. We use an iMac and two eMacs for the teen digital film club and have also just been given a white macbook specifically for production. So -
We (my teen assistant and I) had been able to move files over to the drive manually before. But, on getting the macbook, I got some raw film footage onto it, edited it, and then wanted to get that film onto the mybook in order to make room for a second hour of film to be edited on the macbook. But -
As I tried to show my colleague how to connect the external drive to the macbook, some message came up very quickly - did I want to use the mybook to back up the macbook using Time Machine? I tried to click "no" - there was a scary warning about losing all the info on the drive, and I did not want that to happen! I just wanted to be able to move stuff between the computers and the drive, as we have been doing. I don't know what I did wrong, but, after connecting the drive to the macbook, there is an empty file on the external drive which has the same name as the new macbook, and we can no longer copy anything manually. How can I correct this?

Just to let everyone know: my problem is solved - after a fashion.
When I contacted customer support, I got told the formatting of the drive was not a problem; they sent them out this way so they would be universally compatible. But, since we were sharing the drive between macs, the tech support person thought it would be a good idea to reformat it. He also explained that the original formatting didn't allow transfers of more than 4 gigs - a problem for us, since we are regularly working with larger files.
So he told us how to reformat using disc utility in Leopard. And then we discovered our second problem. The disc could not be reformatted. Nor could it be verified or repaired. It is too damaged to use.
We now have a case number and therefore should be able to replace the hard drive. So that's what happened.

Copy Sales Order with reference to a Contract

Hello,
how can I create a copy of a sales order referred to a contract mantaining the reference?
I have an order referred to a contract; I would like to create a new order in copy ( va01 - create with Reference) maintaining the relationship to the contract.
Thank to all,
Antonio

Hi,
You can create a new order by referring to a contract by clicking on "Create with reference".
Click on Contract and enter the contract number here.You can change teh requested delivery date manually.
Click on Copy.
Before this,make sure that the copy controls have been mainatined for these two document types.
Regards,
Krishna.
Note:Please search in the forum before posting basic questions.

Jax-ws deployed in standalone client fails with nullpointerexception

I have a project which has deployed successfully as a standalone client with deployed jar files wlfullclient.jar, etc. When I add the jax-ws functions that I require, the deployed client fails with a nullpointerexception that is generated from the constructor of the Service class. The project runs successfully within the JDeveloper 11.1.1.5 environment and on a weblogic 10.3 server platform, but fails when I deploy as a standalone client with the wlfullclient.jar. I'm using JDK 1.6.0_24. In testing, the error occurs when I replace the {WLHome}\server\lib\weblogic.jar entry in the classpath with the wlfullclient.jar.
I tested from another angle by creating my jax-ws functions in a standalone deployment, and it works successfully communicates with the webservices. No additional entries on the classpath besides my deployed jar. I then added to my deployment a simple JMS context lookup:
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, contextFactoryProvider);
ht.put(Context.PROVIDER_URL, urlString);
Context context = new InitialContext(ht);
This test runs without error in the JDeveloper environment. As soon as I add the wlfullclient.jar in the standalone environment, I get the following exception:
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/xml/ws/spi/ProviderImpl
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)
at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
at javax.xml.ws.spi.FactoryFinder.safeLoadClass(FactoryFinder.java:150)
at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:30)
at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:90)
at javax.xml.ws.spi.Provider.provider(Provider.java:83)
at javax.xml.ws.Service.<init>(Service.java:56)
Interestingly, there is a class com/sun/xml/internal/ws.spi/ProviderImpl in the {JAVA_HOME}/jre/lib/rt.jar file, and I suppose this is what is used by the jax-ws classes when the wlfullclient.jar is not present on the classpath.
So, what is it that I am missing in how to get the jax-ws classes and the jms classes to work in the standalone deployment environment (outside of the JDeveloper environment).
Edited by: user3653687 on Jan 9, 2012 1:38 PM
Edited by: user3653687 on Jan 9, 2012 2:49 PM

Here is how I solved this problem to execute the application from a jar file (using Oracle Fusion Middleware 11.1.1.5.0 distribution). The key seems to be to extract the contents of the wseeclient.zip file into the same directory as the wlfullclient.jar and ws.api_1.1.0.0.jar files and then ensure that these 2 jars are on the classpath.
In JDeveloper, create a project that has the jms/jax-ws classes.
Put the following text entries to form the classpath (along with other dependent jars, e.g. org.eclipse.persistence...) into a file which will be included in the manifest for the client jar. Be sure to separate entries with a space.
lib/wlfullclient.jar lib/wseeclient.jar lib\ws.api_1.1.0.0.jar lib\org.eclipse.persistence_1.1.0.0_2-1.jar
In the Edit Deployment Profile Properties, select Include Manifest File, specify the main class to execute, and Add the classpath file to be included in the manifest.
Deploy the jar file.
In a deployment area, create the directory that will contain all the classpath jars (e.g. ./lib).
Within the directory ./lib, extract all files from wseeclient.zip (found in {weblogic home}/server/lib)
Copy wlfullclient.jar into the directory ./lib from the {weblogic home}/server/lib
Copy ws.api_1.1.0.0.jar into the directory ./lib from {oracle middleware home}modules
Copy org.eclipse.persistence_1.1.0.0_2-1.jar (for jaxb support) itno the directory ./lib from {oracle middleware home}/modules
Copy the deployed client jar to the deployment area and execute, e.g.:
java -jar ClientTest.jar myArguments

KE28 with" Copy Characteristic Value with Reference Data" doesn't work

Hi experts:
We need to make a top-down setting the processing option 'Copy Characteristic Value with Reference Data'. We have the following source data:
Customer Business Unit Value field.
6        #              100
On the other hand, we have plan data as reference data:
Customer Business Unit Value field.
       A              40
       C              40
       D              20
We need to run a top-down to distribute from client to Business Unit but copying client of reference data. Then, we set 'Copy Characteristic Value with Reference Data' and, in the selection criteria we set '*' for customer.
After running, the result is that the system can find 1 sender and 3 receivers. It is exactly what we are expecting. However, program doesn't make individual items and anything is distributed.
We have found notes 1086282 and 1273924 but the result is the same after implementing these notes.
Thanks in advance for your help.
Best regards
Jose

There are some restrictions on the XML Schema format that you can report off of in Crystal Reports.
If you're using the ODBC XML driver, you may find this of relevance:
[http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xml_data_sources.pdf|http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xml_data_sources.pdf]
and if you're using the native XML driver, the following gives a guide for the accepted formats:
[http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xi_native_xml_driver.pdf|http://resources.businessobjects.com/support/communitycs/TechnicalPapers/cr_xi_native_xml_driver.pdf]
Sincerely,
Ted Ueda

Can I copy between systems with different R/3 releases/add-ons?

hi,all
help me!

Notes 19574 and 24853 provide basic information about this. The main or basic release must always be identical. Support Packages and add-ons should also have the same status in both systems. Only then can the consistency of the data be guaranteed.
For instance, if an add-on is only installed in the source system, the remote copy will terminate with a reference to differences in the dictionary or missing tables in the analysis phase, and will not make the copy. The remote copy terminates if not all data can be copied, in other words if, for instance, a field is missing in the target system, a field is too small or a complete table is missing. You can include individual tables and, from Release WAS 6.10, also development packages (formerly development classes) in the source system in an exception list, to avoid the termination. See note 557132 for further information.
The export does not experience this problem with the transport because the target system is not checked during the export. On the other hand, differences in the dictionary or missing tables are subsequently reported as errors during the import but this does not result in any termination. All of the data that can be imported is imported. In this respect, different ADD-ONs would not pose a problem for the client transport. to what extent is the data consistent or useable?

Method names on "Client Request with Return" nodes

I wasn't sure whether this question would be better here, or in the "integration"
group. The traffic there is somewhat lighter than in here, so perhaps someone
is more likely to read it here :) .
I have two questions about the "method name" in a "Client Request with Return"
node in a Java Process Definition. Apparently the method name is exposed in the
WSDL. I can sort of understand what this method name is used for in the "request"
node, but I fail to understand what the method name corresponds to in the "reply/response"
node of the pair of two nodes. Why does this need to expose a method name in
the WSDL when the point of the node is just to send back a response to the original
request?
Second, in the "Guide to Building Business Processes" document, in the section
titled "Naming the Methods on Client Request with Return Nodes" (page 3-14 in
my copy), the last sentence says "The name must be a valid Java class name".
Is this true? That confuses me.

What do you think is happening here? Specifically if a socket is a connected and a new one comes in. What then?
private void listen() {
          try {
               clientSocket = serverSocket.accept();
          } catch (IOException e) {
               e.printStackTrace();
     }

The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the error 0x80042316

When using Microsoft Backup on a Windows Server 2008 SP2 (not R2 - [Microsoft version 6.0.6002]) I get the error "The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the
error 0x80042316"
The odd thing is that when I start the backup manually, it works fine. When it runs automatically the error appears.
When doing a SFC /scannow I do get errors that can't be corrected.
Is there anything short of rebuilding this machine (It's a DC and the only one this office has) I can do to fix this?

Hi,
0x80042316 means "Another shadow copy creation is already in progress". This error could occur when another VSS instance is running.
Is there any third party backup application installed? Try to uninstall it to see the result. And please also check if there is another backup schedule which causes the conflict.
Meanwhile please provide the result of:
vssadmin list providers
vssadmin list writers
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Hi,
I do have Crashplan ProE running. It started at 1900 and the Windows Backup starts at 2000. I have modified Crashplan not to start until 2300 to see if that helps.
Also:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
AND:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {f0c7ee55-5885-4894-8dd3-14fffbdd4d2e}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {017a0133-7577-4322-b513-04f72404b70a}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {6b17d670-9ea8-4ff1-a59e-b474f4b893db}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {56aad1bf-9bf1-4fde-b2f4-a706577c632d}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e942d09d-276e-450a-9bf4-b1d5abe6af8a}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {3737164b-61ac-454c-b1f7-42f2620f10db}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {39458257-aca4-481e-a302-994f3eb1e9a3}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {6a8ab4aa-760c-4102-a27f-58f570c9c572}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {53577013-8397-448e-9a25-c7cac08aa0a8}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {ee2c9173-92e7-455c-8f73-601647c0ddb2}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {b1f60392-9dfd-4e3a-bda6-3dc2cb622ba4}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a328aede-78f0-448e-9c36-e8379e9fe2a8}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {c39fa334-5c9d-4906-a3b5-33c3444948e6}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {3c9c5584-b5fd-48cf-8541-0c8bfa585ca0}
State: [1] Stable
Last error: No error

Copy client manually with TP-commando

Similar Messages

Maybe you are looking for