SUP changes update source on WSUS

So im trying to set up the SUP on SCCM. initially i had the WSUS installed on another server along with SUP. SCCM would never get updates because WSUS would change its source to itself(sync from an upstream source which was the server it was on) and not
update. If i change the source to sync from microsoft, SCCM would then be able to get updates. so after uninstalling the role and reinstalling the WSUS, the issue still remained and i decided to install the WSUS on the primary server and go from there. Now,
that the WSUS is on the primary server, the update source gets changed to reflect the old server that it was previously on. i have tried rebooting the servers and the SUP settings are also set to pickup updates from microsoft. Has anyone else encountered this
issue?

I understand that WSUS shouldnt be configured because the ConfigMgr does the configuration.. ConfigMgr is configuring the settings incorrectly. Like stated before, the SUP is configured to get updates from microsoft but in WCM.log it states "Successfully
configured WSUS Server settings and Upstream Server to another
server"
WCM.log should read "Successfully
configured WSUS Server settings and Upstream Server to microsoft"

Similar Messages

Cannot insert more than 1 WSUS update source with different unique ids

Hello LnG
I am aware that are a whole bunch of forum threads on this error however little bit of additional help would be of great help, as I have nearly tracked this 'pain' down.
Our environment: SCCM 2007 R3
1 Central
15 Primaries and a whole bunch of secondaries
Single WSUS server
OK, so we have just taken handover of this new account and still getting a hang of the creek and corners in the environment. We have about 1000 machines sitting in "Failed to download updates" state. Error
= 0x80040694
WUAHandler.log:
Its a WSUS Update Source type ({A2762CA9-9739-4260-9C3A-DC4B36122E16}), adding it
Cannot insert more than 1 WSUS update source with different unique ids
Failed to Add Update Source for WUAgent of type (2) and id ({A2762CA9-9739-4260-9C3A-DC4B36122E16}). Error = 0x80040694.
Its a WSUS Update Source type ({BCB9D60B-2668-459B-BFFD-6DDD11AADC53}), adding it
Existing WUA Managed server was already set (http://WSUSServername:8530), skipping Group Policy registration.
Added Update Source ({BCB9D60B-2668-459B-BFFD-6DDD11AADC53}) of content type: 2
WUAHandler
Async searching of updates using WUAgent started.
Checked the
CI_UpdateSources table and found 2 Update sources unique ids:
{BCB9D60B-2668-459B-BFFD-6DDD11AADC53} Date Created 2011-01-11 03:47:52.000/Date Modified 2011-01-11 03:47:52.000
and
{A2762CA9-9739-4260-9C3A-DC4B36122E16} Date Created 2014-07-09 02:48:46.000 / Date Modified 2014-07-09 02:48:46.000
My questions:
Can I rely on the last modified/created date for inactive update source and delete it off the database? in this case can I delete {BCB9D60B-2668-459B-BFFD-6DDD11AADC53}?
When i browsed to the registry location on the Central Server
HKLM\Software\Wow6432Node\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER i saw the update source as {BCB9D60B-2668-459B-BFFD-6DDD11AADC53}.
Does it imply that a stale record?
Any help/guidance will be much appreciated :)

Well!! My wsyncmgr.log says this:
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX1 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX2 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX3 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX4 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX5to 1
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX6 to 18
So, this is an active update source! ?? I cannnot uninstall and reinstall SUP currently. Any thoughts?? Any ody?

Sync failed: WSUS update source not found on site 786. Please refer to WCM.log for configuration error details.

Hi,
I have installed SC 2012 SP1 + SQL Server 2012 CU2e
I followed the following guide:
http://www.windows-noob.com/forums/index.php?/topic/4427-using-sccm-2012-rc-in-a-lab-part-2-add-sup-and-wds/
And when Sync Failed, what could be went wrong?
I have copied the logs+screenshot, and would be thankful if someone can give expert advise.
Here is link : http://sdrv.ms/13kmHBQ
N.A.Malik

Hi,
I haven't tested myself but going to test the following:
WSUS is bit cranky for now but here is what I did to fix it:
1) Uninstall SUP role
2. Uninstall WSUS
4. Delete SUSDB from SQL Server if any
5. Restart Server
6. Install WSUS (Chose to install DB not WID)
7. Configured Updates to be stored locally
8. Run Post Deployment Configuration from Server manager
9. Started WSUS Admin Console and ran Wizard (also chose to connect for the catalog sync) up to the Point where you select the products. Here I canceled the wizard without choosing any products
10. Install SUP role in SCCM and configure the right Settings (WSUS on Server 2012 Defaults to its own admin Website and ports 8530 and 8531) and select the products you required.
11. Check following log file if WSUS does not sync with SCCM.
Path: C:\Program Files\Microsoft Configuration Manager\Logs
File Name:
WCM.log
wsyncmgr.log
12.) Starts synchronization in the sccm console
Source:
http://robiulislam.wordpress.com/2013/04/12/sccm-2012-installation/
N.A.Malik

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

SUP not in sync with WSUS

we recently sttod-up our sccm 2012 environment. We are still in configuration phase per se.
our CAS server also has the SUP role. We installed WSUS on the server prior to setting up the SUP role.
Nothing is showing up in the Software Library. We have not seen anything that stands out in log.
We have not found any article that addresses how to troubleshoot issue.
the servers are all 2008 R2 with SP. the storage for the WSUS files is considered local and WSUS was setup using Windows Internal Database.
Any directions?
Michael Pace Client Services Team Allegis Group, Inc.

Thanks Jorgen;
WSUSCtrl.log does nor show any arrors. however the SMS_WSUS_CONFIGURATION_MANAGER and SMS_WSUS_CONTROL_MANAGER indicate many errors.
extract of logs as follows.
SMS_WSUS_CONFIGURATION_MANAGER :
Error Milestone CAS 10/11/2012 8:31:51 AM SCCM2012CAS.allegisgroup.com SMS_WSUS_CONFIGURATION_MANAGER 6600 WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "SCCM2012CAS.allegisgroup.com".
Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured
on the WSUS IIS website.
SMS_WSUS_CONTROL_MANAGER :
Error Milestone CAS 10/11/2012 8:26:04 AM SCCM2012CAS.allegisgroup.com SMS_WSUS_SYNC_MANAGER 6703 WSUS Synchronization failed.   Message: WSUS server not configured. Please refer to WCM.log for configuration
error details..   Source: CWSyncMgr::DoSync.    The operating system reported error 2147500037: Unspecified error
WCM.log:
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:27:48 AM 6232 (0x1858)
Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:12 AM 6232 (0x1858)
Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:12 AM 6232 (0x1858)
Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:13 AM 6232 (0x1858)
Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:13 AM 6232 (0x1858)
Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:14 AM 6232 (0x1858)
Successfully connected to server: SCCM2012CAS.allegisgroup.com, port: 80, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
Not yet ready to set WSUS Server subscription as returned by WSUS Server. Will try again. SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
This error is transient and will be retried in 1 minutes. SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:28:19 AM 6232 (0x1858)
Wait timed out after 1 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:29:19 AM 6232 (0x1858)
Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 10/10/2012 10:29:24 AM 6232 (0x1858).
thanks again
Michael Pace Client Services Team Allegis Group, Inc.

Failed to Add Update Source for WUAgent Error = 0x87d00692 - HELP!!

I am having trouble with my clients recieving updates. I notice alot of my clients where my primary site is are recieving updates but all of my clients in my secondary sites are not. Below is output from the WUAHandler.log on a client system.
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server HTTPS://SERVER.COMPANY.COM:443 and Policy ENABLED WUAHandler 4/12/2013 8:21:28 AM 4220 (0x107C)
Failed to Add Update Source for WUAgent of type (2) and id ({AA27FC20-A281-46CC-B04F-D0940B5E072F}). Error = 0x87d00692. WUAHandler 4/12/2013 8:21:28 AM 4220 (0x107C)
The server stated above is correct and we have no GPOs applied to our enviornment for an update server.
I did just update to SCCM 2012 SP1 and have applied all the hotfixes for WSUS. I am at a roadblock. Would a site reset be advised? Perhaps WSUS and SUP reinstall? Any help would be appreciated I am out of ideas.
My enviornment:
1 primary server - roles- sup, dp, mp
3 secondary sites - role - dp and mp - clients under these sites do not get updates
Ryan Ventimiglio

When I have checked this my current SCCM server address thats listed in the WUAHandler log is set in the registry for the client. So this is the same address so its not like anything is conflicting.
Whats strange about this is that everything was working fine before the SP1 upgrade. I just ran a site reset but no change. Do you think a WSUS/SUP uninstall/reinstall would be the next step? Is this done typically? Any other
things I should be checking. I know we do not have any GPOs set in our enviornment for this so this cant be the problem.
Ryan Ventimiglio

Automating Importing a Visio OLE Object or Changing the Source of a Previously Imported OLE Object

My colleagues and I import our Visio files into FrameMaker 10 via the following mechanism: File > Import > Object... > Create from File (with Link checked). We do this because, for us, the benefits of object linking and embedding outweight the pitfalls. In order to institute and automate a graphic file naming convention, I want to be able to do one of the following using ExtendScript:
Replace each Visio OLE object with that of a renamed or new Visio file. (I've tried using the Import() method with many different import-script settings, but have not found the correct import-script, if such a thing exists for importing Visio files imported by reference and linked as OLE objects. My typical error when attempting this is FV_DisallowedImportType, which indicates the source file type is disallowed by my import-script settings. When I talk about my import-script settings, I'm referring to the adjustments that I make to the parameters returned from a call to GetImportDefaultParams(). I've tried numerous import-script combinations but have had no luck. )
Rename the Visio source file and change the source file of an already-linked Visio OLE object. (To do this, I need to determine how to implement a script that equals the following user actions while a FM document is open: clicking on Links... under the Edit menu to bring-up the Links window; selecting each link displayed in the Links window; clicking the Change Source button for each selected link; entering the new file name in the File name field of the Change Source window; clicking Open. Needless to say, I found nothing in the ExtendScript capabilities that indicates that this approach is doable. It may be doable using FDK F_Codes, I haven't explored that avenue and would like to avoid it.)
Modify the OLE2 facet such that it points to the renamed file instead of the previous name for the file. (This does not seem like a clean approach. As is the case now, I don't know how to properly update the facet with the new file name. I've experimented with simply changing the file name strings from new to old, but that does not work. There's probably some error-checking or checksum that needs to be recomputed. Bottom line: I don't know enough about facets.)
Any help would be greatly appreciated.
Thanks, Paul

Hi Paul,
I tried doing something like this years ago with FrameScript, but found out that the OLE stuff is not exposed to FrameScript or the FDK. So it is probably not exposed to ExtendScript either. When you query an OLE graphic's InsetFile property, it returns a null string, the same as a graphic Imported by Copy would. As far as I can see, importing as an OLE object is only available through the Windows FrameMaker interface.
Rick

How to change the source level in java Studio creator

Hi,
I am using Sun Java Studio Creator 2 Update 1 IDE, in this IDE how to change the source level to 1.5 for an existing project.
Thanks in advance,
Rajesh.

Hi!
Unfortunately Sun Java Studio Creator 2 Update 1 doesn't support 1.5 source level. But You can try to download NetBeans IDE (from http://www.netbeans.org) and there with Visual Web project You will find the same functionality as for Creator. And 1.5 source level is supported by NetBeans.
Thanks,
Roman.

SCCM 2007 R3 Software Updates Sync : 6703 WSUS server not configured

Hi,
We run SCCM 2007 R3 in native mode (Software Update Point and WSUS both reside on SCCM site server). We're having issues running Software Updates Synchronization which have previously worked fine. In SMS_WSUS_Control_Manager the errors appear as follows
MessageID:6703
SMS WSUS Synchronization failed.
Message: WSUS server not configured.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error
I've followed the suggested fixes in
http://technet.micro...y/bb735874.aspx but still we have an issue.
If I open the WSUS console directly and run a manual synchronization from Microsoft this completes successfully. However, I presume this will not be using SSL which is what SCCM will want to use in native mode. I've checked the bindings in IIS on WSUS Administration
site to confirm that the certificate hasn't expired.
Any ideas what else I can try?
Cheers,
Paul

wsyncmgr.log repeatedly contains the following
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER 13/10/2013 14:02:11 612 (0x0264)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CCPSCCM02 SITE=WES PID=8084 TID=612 GMTDATE=Sun Oct 13 13:02:11.288 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 13/10/2013
14:02:11 612 (0x0264)
Sync failed: WSUS server not configured. Source: CWSyncMgr::DoSync SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CCPSCCM02 SITE=WES PID=8084 TID=612 GMTDATE=Sun Oct 13 13:07:11.284 2013 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)
Sync time: 0d00h05m00s SMS_WSUS_SYNC_MANAGER 13/10/2013 14:07:11 612 (0x0264)

RFWT0020 withholding tax data - Data Regen vs. Change to Source Tax Code?

Can anyone explain the difference between these two options when running RFWT0020 to update withholding tax data? Data Regeneration vs. Changes to Source Tax Code? I can't find any mention of the two options in the program documentation
When I do test runs with the two different options, the program is selecting difference documents to update. If we are just turning on the 1099 functionality now (beginning with the 2011 tax year), should I run the program once with Regeneration mode and once with Changes to Source Tax Code???
Thanks for any advice!
Allison

Hi,
he program enables the withholding tax code to be changed for reconciled and open items with existing withholding tax data. For this, the tax rate of the existing withholding tax data as well as the tax rate of the new withholding tax code must be 0%. The new withholding tax codes are taken from the customer or vendor master data. In the case of extended withholding tax, the withholding tax code is only changed if the related withholding tax categories are the same. The withholding tax base amount is not changed by this procedure.
Recreating or changing the withholding tax data requires that the program first be executed for invoices and then executed for payments in a subsequent step.
When you start the program, the selection screen appears. You can make selections according to vendors, tax code 1, tax code 2 (vendor master record), customers, tax code 1, tax code 2 (customer master record), company codes, document numbers and posting data. The selection determines which items are checked for possible subsequent entries in tables BSEG, BSAK, BSIK, BSAD, BSID, WITH_ITEM.
You can also decide whether only withholding tax data is to be handled for cases where the documents in question contain no withholding tax data. There is no withholding tax data if no withholding tax entries exist for the item selected in table WITH_ITEM (extended withholding tax) or the die withholding tax fields in table BSEG are not filled.
The selection can also be made in test mode. If you do this, no changes are made in the database. You are therefore advised to run the program in test mode initially.
Regards
Aditya

Changing Data Source for command objects

Hi,
My report (designed in CR 10) is running based on the Stored Procedure call using a command object; which is running successfully in the DEV environment. The report data source connectivity is a DSN.
Now i want to switch it to QA environment with different DSN name. When i tried to update the Change Data Source option, it doesn't allows to update the existing command with a new command!!!!
I don't know how to fix this. Could any one of you have idea, pls. share it here???
Thanks
Viswa

If you have same table structure in new data source then you can change the datasource connection.
Follow the steps in this article
KBase Article ID:c2016958
Article refers to:Crystal Reports 10
Symptom
In Crystal Reports (CR) 10, can you change the database connection of an existing command object to use a different database connection without the use of a Crystal Repository?
Resolution
Yes, you can change the database connection of an existing command object to use a different database connection without the use of a Crystal Repository by using the following steps:
====================
NOTE:
You must apply the CR 10 Monthly Hot Fix (cr10win_en.zip) and the CR 10 Database and Export Drivers Monthly Hot Fix (dbex10win_en.zip) before starting the steps below.
You can download these hot fixes at http://support.businessobjects.com/search
====================
1. Open a report with a command object.
2. Go the 'Database' menu and click 'Set Datasource Location'.
3. In the 'Set Datasource Location' dialog box, select the connection for the command object (the connection appears as a cylinder with a plug).
4. In the lower window, select the new connection and log on to the database.
5. Ensure the connection is highlighted for the command object in the top window, and the connection is highlighted for the new command object in the bottom window.
6. Click Update.
The database connection for the command object now changes to use the new database connection information.
Regards,
Raghavendra

Change of Source System in OBIA 7.9.6.4

hi All
Our Client has decided to change the source system from EBS R11 to EBS R12.So they have completed EBS migration to R12.I have been asigned a job to
configure the existing bi apps for the source EBS R12 which previosly was using EBS R11. Can any one help me to configure the OBI Apps Financial module.
Our OBIEE version is 11.1.1.6.9
OBIA version is 7.9.6.4
Any help will be appreciated as the Oracle's online doc is also not helping me.
Thanks & Regards
Bivin

Hi Bivin & Srini,
I am working on this and keep post my updates.please do from your end too.
Thanks &Regards,
Raj

Change of source system - any mass transaction?

Hi,
we have to transfer some programs and stuff from one system to another. Basis people will manually import a transport for this. In target system, I want to change the source system of the transported objects. Because it is quite a big number, I am looking for a standard reoprt/transaction to accomplish that.
Any hints?
TIA,
Regards,
Clemens

Hi
I believe yuo can create a program to update the table TRDIR, something like this:
TABLES: TADIR.                         " Catalogo oggetti R/3 Repository
DATA: COUNT TYPE I.
PARAMETERS: P_SYST1 LIKE TADIR-SRCSYSTEM, " Source Sys
            P_CLASS LIKE TADIR-DEVCLASS ,
            P_SYST2 LIKE TADIR-SRCSYSTEM. " Target Sys.
SELECT * FROM TADIR WHERE SRCSYSTEM = P_SYST1
                      AND DEVCLASS = P_CLASS.
TADIR-SRCSYSTEM = P_SYST2.
MODIFY TADIR.
IF SY-SUBRC = 0.
    COUNT = COUNT + 1.
ENDIF.
ENDSELECT.
IF SY-SUBRC = 0.
   WRITE: Count, 'Objects from', P_SYST1, 'to', P_SYST2.
ENDIF.
U can try to use the trx SE03:
- Run the node: Change Objects Directoty entries
Here you can change the dev class and source system too, but I don't believe it can change all objects in mass way.
Max

ConfigMgr 2012 Update Source content deleted

Greetings,
I am experiencing a problem that is appears to be the same as the old thread here:
http://social.technet.microsoft.com/Forums/en-US/bee18ffb-f779-4aa4-900d-046e7711424c/sccm-2012-source-content-gets-deleted?forum=configmanagergeneral
Rather than revive an old post, I thought it best to start my own.
We have a rather large environment (CAS +5 Primaries + Many DP's) and we are currently adding several new remote DP's each week. Each time a new DP is added it is placed in a Distribution Group and the "core" package content is sent
to it.
I have a problem where my Windows Update Packages keep failing due to content disappearing from the source folder location. This started some time ago, and is now becoming a regular event to correct. Not every day, but once a week or so.
The Update group has the updates all showing as "downloaded"
I have a report query that matches the updates to the "GUID" subfolder so I know all the content is there
I distribute the content from the CAS. Distrmgr.log shows all is good. Packagemgr.log on the Primaries show all is good
Client have been installing the updates as expected so the deployment does work
Days/weeks later, ALL the DP's will show as "failed" for that update package. Checking the distmgr.log shows that it is failing to distribute due to a missing source folder. I use my query to work out which update that subfolder GUID belongs to,
but it is already flagged as downloaded, and when trying to download it again CM just "skips" it thinking it already has the content in that package.
The "fix" is to download the same update to a new package instead. CM then does a proper check, realises it doesn't have the content and will download the update to the new package source location. I can then copy the missing GUID subfolder
from the new package into the original package and try the distribution again.
The problem now is that there are usually many folders missing, so distmgr.log will fail again on the next missing folder. Because it stops at the first error, repeating the above process is incredibly tedious when there are a lot of missing folders.
My current "solution" is to select ALL the updates that should be in the current package and download them all to a "Temp package" that isn't deployed or distributed anywhere. Then in future when the main deployment package fails, I just
"select all, copy" the contents of the temp folder into the original folder (skip duplicates) and it puts back all the missing content and distribution will work again.
We are not using ADR's for this content, although I do have an ADR for the Endpoint updates which go into a completely different distribution package.
*Something* is cleaning up or purging these folders from the source location, but I have no idea what process or mechanism this might be.
Any thoughts or suggestions most welcome.
Scott.

I've found the cause, blog post write here:
http://kickthatcomputer.wordpress.com/2014/10/11/configuration-manager-update-source-content-being-deleted/
Microsoft was working with me trying to identify what was deleting the folders, however nothing was appearing as the cause.
I just realised this morning that I had used the built-in CM12 Migration function some time back to migrate update packages and groups over to our second hierarchy but hadn't updated any of the migrated content since then. The migrated packages on the second
hierarchy still point to the same source location and so whenever my original hierarchy added content to the update packages, the second hierarchy would delete it because it though it was "orphaned" content.
This is something people will have to watch out for when using the migration wizard as the same type of issues will impact things like WIM boot image packages as well where the source content can be manipulated directly by the CM12 system on one hierarchy
without the other one being aware of that change.
At the moment the options are to either
Make sure you run a "migrate changes" job whenever you make changes to updates on your source hierarchy to keep them in sync
Manually make a copy of the source content to a different folder or location, then update the package source location on the migrated packages to point to that new content (undesirable for massively large content)
Create a scripted method to schedule regular migration jobs between the hierarchies (looking into this option now)

Automatic Deployed Updates Source Cleanup

I recently set up an automatic deployment rule for the scep definition updates. It works like a charm, new update are being downloaded, and old updates are beeing superseeded and at last expired.
But, the source folder, where my software update deployment package lies is just getting bigger and bigger. SCCM obviously don't distribute the expired updates to the DP anymore but does not cleanup the source folder.
Is there a mechanism which will cleanup my source folder or do i need to write a script for that? I also run the WSUS Cleanup Wizard, but it also won't cleanup my update source folder.
We are using SCCM 2012 SP1 CU3
Thanks in advance..

You should remove the expired updates from your software update Groups. That way the source and the DP will be "cleaned up"
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

SUP changes update source on WSUS

Similar Messages

Maybe you are looking for