Can not find the mixer program "sndvol32"

I get this message when choosing windows recording mixer from edit view. If anyone can share knowledge it would be most appreciated. I am using Adobe Audition 2.0 on a Dell Studio 15 with Vista.

I'm guessing AA2.0 didn't know about how Vista has moved some files to different locations... That particular feature in AA2.0 may not work under Vista... Maybe a durin or ozpeter can tell you for sure...

Similar Messages

Suddenly all of my Office-programs have stopped working and will not launch on my MacBook. Could anyone give an amateur from Norway a hint of what may cause the problem? And I can not find the installation-disc for Office...Super! :)

Suddenly all of my Office-programs have stopped working and will not launch on my MacBook. They were all already installed when I bought the computer. Could anyone give an amateur from Norway a hint of what may cause the problem? (And I can not find the installation-disc for the Office Programs...Super!)

Have you contacted Microsoft support - http://www.microsoft.com/mac/support ?

Windows Vista home addition want let Icloud execute. I went into the DEP program but I can not find the Apple exe file to add as ok. What is the file name?

Windows Vista home additon want let Iclud execute. I went into the DEP program but I can not find the Apple exe file to add as ok. What is the file name?

Hey,
if you know the name(s) of the root folder(s) you want to access (eg. by making a note on the Windows side) then you can make them appear by just doing Shift-Command-G in Finder ("Go to Folder…"), and entering the full path to the required folders. You can then navigate all the contents as normal.
HTH,
S.

Hi, Need help. I am trying to download the latest iTunes for Windows application but on running the program it says that it can not be completed as it can not find the folder location of the file "iTunes.msi" . Any clues would be appreciated

Hi, Need help. I am trying to download the latest iTunes for Windows application but on running the program it says that it can not be completed as it can not find the folder location of the file "iTunes.msi" . Any clues would be appreciated

(1) Download the Windows Installer CleanUp utility installer file (msicuu2.exe) from the following Major Geeks page (use one of the links under the "DOWNLOAD LOCATIONS" thingy on the Major Geeks page):
http://majorgeeks.com/download.php?det=4459
(2) Doubleclick the msicuu2.exe file and follow the prompts to install the Windows Installer CleanUp utility. (If you're on a Windows Vista or Windows 7 system and you get a Code 800A0046 error message when doubleclicking the msicuu2.exe file, try instead right-clicking on the msicuu2.exe file and selecting "Run as administrator".)
(3) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
(4) In the list of programs that appears in CleanUp, select any iTunes entries and click "Remove", as per the following screenshot:
(5) Quit out of CleanUp, restart the PC and try another iTunes install. Does it go through properly this time?

My program can not find the help file

I just downloaded JavaHelp. I can run all the examples. However when I recompile using Forte, the Merge Example it can not find the "master.hs" file. I suspect that I have something configured wrong.
I put all the help files in the same directory as the source code.

The helpset hs file is specified relative to the class from which it is referred. If the class & hs are in the same dir
URL hsUrl=HelpSet.findHelpSet(null, "master.hs");
hs=new HelpSet(null, hsUrl);

Help:Can not find the file in jar!

Hello everyone:
I build a project using Netbeans 5.0 and make a jar file with it...
The code in the project as follows will throw an exception described that it can not find the file named datasource-config.xml
String dataFilePath = getClass().getResource(dataFile).getPath();
//System.out.println("filepath:"+dataFilePath);
InputStream input = new FileInputStream(dataFilePath);
when I run the project with the main() function as an entry it works perfectly and output:
filepath:/C:/projects/java_project/search/build/classes/com/cn/wxjt/lucene/config/datasource-config.xml
But when I compressed the project with jar and run it , it will show:
filepath:file:/C:/projects/java_project/search/dist/search.jar!/com/cn/wxjt/lucene/config/datasource-config.xml
there is a (!) between search.jar and /com/cn/wxjt...
I dont know why I generate a ! symbol in the file path... Is it cause the exception->
java.io.FileNotFoundException: file:\C:\projects\java_project\search\dist\search.jar!\com\cn\wxjt\lucene\config\datasource-config.xml
If you have any idea, plz tell me.
Thank you and best wishes to you !
:)

If the file you want to read is in your jar file, use
getClass ().getResourceAsStream
(relative_path_file_name)Hope that help,
Jackhey jack i want to open the file as new File
i m using this.getClass().getResource("resource/backend.xml");
the resource is the directory inside the jar file.
when i prints the url it shows:
the jar file is in the WORK directory
URL : jar:file:/home/neeraj/WORK/show.jar!/resource/backend.xml
now when i creates new File using the url.getFile() method the file does not exist.
although the same programs runs well when i uses the InputStream
so plz tell me cant I create a new File from the above method????
thanks in advance
with regards
neeraj

Can not find the the RBS tables after installing the Remote Blog Storage

Hi,
I am trying to configure the Remote Blob storage on my Sharepoint Server 2013. I am using the SQL Server Express 10.50.6000.
Everything is going fine, but I can not find the tables in the Database.
I am not sure where I did the wrong thing.
machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
but the installation is looking for some other.
Thanks in advance.
=== Verbose logging started: 3/23/2015 13:55:09 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (44:F8) [13:55:09:000]: Resetting cached policy values
MSI (c) (44:F8) [13:55:09:000]: Machine policy value 'Debug' is 0
MSI (c) (44:F8) [13:55:09:000]: ******* RunEngine:
******* Product: RBS.msi
******* Action:
******* CommandLine: **********
MSI (c) (44:F8) [13:55:09:000]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (44:F8) [13:55:09:000]: Grabbed execution mutex.
MSI (c) (44:F8) [13:55:09:016]: Cloaking enabled.
MSI (c) (44:F8) [13:55:09:016]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (44:F8) [13:55:09:016]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (90:A4) [13:55:09:016]: Running installation inside multi-package transaction D:\RBS.msi
MSI (s) (90:A4) [13:55:09:016]: Grabbed execution mutex.
MSI (s) (90:34) [13:55:09:016]: Resetting cached policy values
MSI (s) (90:34) [13:55:09:016]: Machine policy value 'Debug' is 0
MSI (s) (90:34) [13:55:09:016]: ******* RunEngine:
******* Product: D:\RBS.msi
******* Action:
******* CommandLine: **********
MSI (s) (90:34) [13:55:09:031]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (90:34) [13:55:09:031]: Setting cached product context: User non-assigned for product: FB42F99F09B0E3646985F32DFE3C9C29
MSI (s) (90:34) [13:55:09:031]: Using cached product context: User non-assigned for product: FB42F99F09B0E3646985F32DFE3C9C29
MSI (s) (90:34) [13:55:09:031]: Setting cached product context: machine assigned for product: 000021599B0090400100000000F01FEC
115C834F46A5E33479CEE53534AD76A0
:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:265]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (90:34) [13:55:09:265]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active
MSI (s) (90:34) [13:55:09:265]: APPCOMPAT: looking for appcompat database entry with ProductCode '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'.
MSI (s) (90:34) [13:55:09:265]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (90:34) [13:55:09:265]: Transforms are not secure.
MSI (s) (90:34) [13:55:09:265]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\rbs_install_log.txt'.
MSI (s) (90:34) [13:55:09:265]: Command Line: TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME=WSS_Content DBINSTANCE=jpntkyint01\sharepoint FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1 CURRENTDIRECTORY=D:\ CLIENTUILEVEL=3 CLIENTPROCESSID=14660
MSI (s) (90:34) [13:55:09:265]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{1AC68E73-94F1-4A01-B229-82B2F73C3326}'.
MSI (s) (90:34) [13:55:09:265]: Product Code passed to Engine.Initialize: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (90:34) [13:55:09:265]: Product Code from property table before transforms: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (90:34) [13:55:09:265]: Product Code from property table after transforms: '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'
MSI (s) (90:34) [13:55:09:265]: Product registered: entering maintenance mode
MSI (s) (90:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:265]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (90:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:265]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is admin assigned: LocalSystem owns the publish key.
MSI (s) (90:34) [13:55:09:265]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is managed.
MSI (s) (90:34) [13:55:09:265]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (90:34) [13:55:09:281]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Specifed source is already in a list.
MSI (s) (90:34) [13:55:09:281]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'DisableBrowse' is 0
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (90:34) [13:55:09:281]: Adding new sources is allowed.
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Package name retrieved from configuration data: 'RBS.msi'
MSI (s) (90:34) [13:55:09:281]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'DisableMsi' is 1
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (90:34) [13:55:09:281]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (90:34) [13:55:09:281]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:281]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is admin assigned: LocalSystem owns the publish key.
MSI (s) (90:34) [13:55:09:281]: Product {56D21E05-679B-40F2-94C1-DB0D7EB2E461} is managed.
MSI (s) (90:34) [13:55:09:281]: Running product '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}' with elevated privileges: Product is assigned.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding TRUSTSERVERCERTIFICATE property. Its value is 'true'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Modifying FILEGROUP property. Its current value is 'default'. Its new value: 'PRIMARY'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding DBNAME property. Its value is 'WSS_Content'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding DBINSTANCE property. Its value is 'jpntkyint01\sharepoint'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Modifying FILESTREAMFILEGROUP property. Its current value is 'default'. Its new value: 'RBSFilestreamProvider'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding FILESTREAMSTORENAME property. Its value is 'FilestreamProvider_1'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (90:34) [13:55:09:281]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '14660'.
MSI (s) (90:34) [13:55:09:281]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (90:34) [13:55:09:328]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '489ffd242e95054781e9ce4b8d0b8aa5'.
MSI (s) (90:34) [13:55:09:328]: RESTART MANAGER: Session opened.
MSI (s) (90:34) [13:55:09:328]: TRANSFORMS property is now:
MSI (s) (90:34) [13:55:09:328]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (90:34) [13:55:09:328]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
MSI (s) (90:34) [13:55:09:328]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\AppData\Roaming
MSI (s) (90:34) [13:55:09:328]: SHELL32::SHGetFolderPath returned: C:\Users\medsvradmin\Favorites
Action ended 13:55:09: AppSearch. Return value 1.
Action start 13:55:09: ValidateProductID.
MSI (s) (90:34) [13:55:09:390]: Skipping action: Sqlmsirc_CheckLanguage_64 (condition is false)
MSI (s) (90:34) [13:55:09:390]: Doing action: CostInitialize
Action ended 13:55:09: ValidateProductID. Return value 1.
MSI (s) (90:34) [13:55:09:406]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (s) (90:34) [13:55:09:406]: Baseline: Sorting baselines for {56D21E05-679B-40F2-94C1-DB0D7EB2E461}.
MSI (s) (90:34) [13:55:09:406]: Baseline: New baseline 10.50.1600 from transaction.
MSI (s) (90:34) [13:55:09:437]: Baseline: Sorted order Native: Order 0.
MSI (s) (90:34) [13:55:09:437]: Baseline Data Table:
MSI (s) (90:34) [13:55:09:437]: ProductCode: {56D21E05-679B-40F2-94C1-DB0D7EB2E461} Version: 10.50.1600 Attributes: 0 PatchId: Native BaselineId: -2147483648 Order: 0
MSI (s) (90:34) [13:55:09:437]: Baseline File Table:
MSI (s) (90:34) [13:55:09:437]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:09:437]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
MSI (s) (90:34) [13:55:09:453]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: Patch
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: MsiPatchHeaders
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: __MsiPatchFileList
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2228 2: 3: PatchPackage 4: SELECT `DiskId`, `PatchId`, `LastSequence` FROM `Media`, `PatchPackage` WHERE `Media`.`DiskId`=`PatchPackage`.`Media_` ORDER BY `DiskId`
MSI (s) (90:34) [13:55:09:453]: Delta compression fallback method for this product transaction is 'MSI 2.0 legacy obsolescence'
MSI (s) (90:34) [13:55:09:453]: Note: 1: 2205 2: 3: Patch
Action start 13:55:09: CostInitialize.
MSI (s) (90:34) [13:55:09:453]: Doing action: FileCost
Action ended 13:55:09: CostInitialize. Return value 1.
MSI (s) (90:34) [13:55:09:468]: Note: 1: 2205 2: 3: Class
MSI (s) (90:34) [13:55:09:468]: Note: 1: 2205 2: 3: Extension
MSI (s) (90:34) [13:55:09:468]: Note: 1: 2205 2: 3: TypeLib
Action start 13:55:09: FileCost.
MSI (s) (90:34) [13:55:09:468]: Doing action: IsolateComponents
Action ended 13:55:09: FileCost. Return value 1.
Action start 13:55:09: IsolateComponents.
MSI (s) (90:34) [13:55:09:468]: Doing action: CostFinalize
GE: Adding ClientDir1025 property. Its value is 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\ar\'.
MSI (s) (90:34) [13:55:09:593]: PROPERTY CHANGE: Modifying ServerDir property. Its current value is 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Server'. Its new value: 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Server\'.
MSI (s) (90:34) [13:55:09:593]: PROPERTY CHANGE: Modifying Eula1033 property. Its current value is 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\1033'. Its new value: 'C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\1033\'.
MSI (s) (90:34) [13:55:09:593]: Target path resolution complete. Dumping Directory table...
MSI (s) (90:34) [13:55:09:593]: Note: target paths subject to change (via custom actions or browsing)
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: TARGETDIR , Object: D:\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: WindowsFolder , Object: C:\Windows\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ProgramFiles64Folder , Object: C:\Program Files\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: INSTALLDIR , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: GAC , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ClientDir , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ClientDir3082 , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\es\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ClientDir1025 , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\ar\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: ServerDir , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Server\
MSI (s) (90:34) [13:55:09:593]: Dir (target): Key: Eula1033 , Object: C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\1033\
MSI (s) (90:34) [13:55:09:593]: Doing action: IsDotNet20Or40Installed
Action ended 13:55:09: CostFinalize. Return value 1.
MSI (s) (90:34) [13:55:09:593]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'IsDotNet20Or40Installed'
MSI (s) (90:34) [13:55:09:609]: Creating MSIHANDLE (1) of type 790542 for thread 9268
MSI (s) (90:6C) [13:55:09:609]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB261.tmp, Entrypoint: IsDotNetFramework20Or40Installed
MSI (s) (90:FC) [13:55:09:609]: Generating random cookie.
MSI (s) (90:FC) [13:55:09:609]: Created Custom Action Server with PID 14944 (0x3A60).
MSI (s) (90:D0) [13:55:09:640]: Running as a service.
MSI (s) (90:D0) [13:55:09:640]: Hello, I'm your 64bit Impersonated custom action server.
MSI (s) (90!08) [13:55:09:640]: PROPERTY CHANGE: Adding DOTNETCOREPATH property. Its value is '1'.
MSI (s) (90!08) [13:55:09:640]: PROPERTY CHANGE: Adding IsDotNet20Or40Installed property. Its value is '1'.
MSI (s) (90:6C) [13:55:09:640]: Closing MSIHANDLE (1) of type 790542 for thread 9268
One or more .NET Framework assemblies found in MsiAssembly table require the GAC, need to check for the .NET Framework
MSI (s) (90:34) [13:55:09:640]: Skipping action: CA_ErrorPrereqDotNet20Or40 (condition is false)
MSI (s) (90:34) [13:55:09:640]: Doing action: SqlFollowComponentsValidate_Redist_64
Action ended 13:55:09: IsDotNet20Or40Installed. Return value 1.
MSI (s) (90:34) [13:55:09:640]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SqlFollowComponentsValidate_Redist_64'
MSI (s) (90:34) [13:55:09:687]: Creating MSIHANDLE (11) of type 790542 for thread 9268
MSI (s) (90:04) [13:55:09:687]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB281.tmp, Entrypoint: SqlFollowComponentsValidate
Action start 13:55:10: InstallServices.
MSI (s) (90:34) [13:55:10:498]: Doing action: StartServices
Action ended 13:55:10: InstallServices. Return value 1.
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2205 2: 3: ServiceControl
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2228 2: 3: ServiceControl 4: SELECT `Name`,`Wait`,`Arguments`,`Event`, `Action` FROM `ServiceControl`, `Component` WHERE `Component_` = `Component` AND (`Action` = 0 OR `Action` = 1 OR `Action` = 2)
Action start 13:55:10: StartServices.
MSI (s) (90:34) [13:55:10:498]: Doing action: RegisterUser
Action ended 13:55:10: StartServices. Return value 1.
Action start 13:55:10: RegisterUser.
MSI (s) (90:34) [13:55:10:498]: Doing action: RegisterProduct
Action ended 13:55:10: RegisterUser. Return value 0.
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
Action start 13:55:10: RegisterProduct.
MSI (s) (90:34) [13:55:10:498]: Doing action: PublishComponents
Action ended 13:55:10: RegisterProduct. Return value 1.
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2205 2: 3: PublishComponent
MSI (s) (90:34) [13:55:10:498]: Note: 1: 2228 2: 3: PublishComponent 4: SELECT `PublishComponent`.`ComponentId`, `PublishComponent`.`Qualifier`, `PublishComponent`.`AppData`, `Feature`, `Component`.`ComponentId`, `Component`.`RuntimeFlags` FROM `PublishComponent`, `Component`, `Feature` WHERE `PublishComponent`.`Component_` = `Component`.`Component` AND `PublishComponent`.`Feature_` = `Feature`.`Feature` AND ((`Feature`.`Action` = 1 OR `Feature`.`Action` = 2) OR (`Feature`.`Action` = 4 AND `Feature`.`Installed` = 0) OR (`Feature`.`Action` = 3 AND (`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR `Feature`.`Installed` = 4)))
Action start 13:55:10: PublishComponents.
MSI (s) (90:34) [13:55:10:498]: Doing action: MsiPublishAssemblies
Action ended 13:55:10: PublishComponents. Return value 0.
Action start 13:55:10: MsiPublishAssemblies.
MSI (s) (90:34) [13:55:10:498]: Doing action: PublishFeatures
Action ended 13:55:10: MsiPublishAssemblies. Return value 1.
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:498]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
Action start 13:55:10: PublishFeatures.
MSI (s) (90:34) [13:55:10:498]: Doing action: PublishProduct
Action ended 13:55:10: PublishFeatures. Return value 1.
MSI (s) (90:34) [13:55:10:513]: Resolving source to launched-from source.
MSI (s) (90:34) [13:55:10:513]: Setting launched-from source as last-used.
MSI (s) (90:34) [13:55:10:513]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:10:513]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'D:\'.
MSI (s) (90:34) [13:55:10:513]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{56D21E05-679B-40F2-94C1-DB0D7EB2E461}'.
MSI (s) (90:34) [13:55:10:513]: SOURCEDIR ==> D:\
MSI (s) (90:34) [13:55:10:513]: SOURCEDIR product ==> {56D21E05-679B-40F2-94C1-DB0D7EB2E461}
MSI (s) (90:34) [13:55:10:529]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (90:34) [13:55:10:529]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:529]: Determining source type
MSI (s) (90:34) [13:55:10:529]: Source type from package 'RBS.msi': 2
MSI (s) (90:34) [13:55:10:529]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{56D21E05-679B-40F2-94C1-DB0D7EB2E461}
MSI (s) (90:34) [13:55:10:623]: SECREPAIR: Hash Value for the file:RBS.msi matched
MSI (s) (90:34) [13:55:10:623]: Source path resolution complete. Dumping Directory table...
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: TARGETDIR , Object: D:\ , LongSubPath: , ShortSubPath:
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: WindowsFolder , Object: D:\ , LongSubPath: , ShortSubPath:
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: ProgramFiles64Folder , Object: D:\ , LongSubPath: Program Files\ , ShortSubPath: PFiles\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: INSTALLDIR , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\ , ShortSubPath: PFiles\jfw2d1_t\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: Eula3082 , Object: D:\ , LongSubPath: Program Files\Microsoft SQL
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: DocsDir , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\Documentation\ , ShortSubPath: PFiles\jfw2d1_t\gsutoqfr\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: MaintainerDir , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\Maintainer\ , ShortSubPath: PFiles\jfw2d1_t\jygjogya\
Files\jfw2d1_t\g-pfawke\pt-PT\
MSI (s) (90:34) [13:55:10:623]: Dir (source): Key: ClientDir2052 , Object: D:\ , LongSubPath: Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\zh-CHS\ , ShortSubPath: PFiles\jfw2d1_t\g-pfawke\zh-CHS\
Action ended 13:55:10: PublishProduct. Return value 1.
MSI (s) (90:34) [13:55:10:638]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:638]: Using cached product context: machine assigned for product: 50E12D65B9762F04491CBDD0E72B4E16
MSI (s) (90:34) [13:55:10:638]: Note: 1: 2205 2: 3: Shortcut
MSI (s) (90:34) [13:55:10:638]: Note: 1: 2228 2: 3: Shortcut 4: SELECT `Shortcut`,`Name`, `FileName`, `Component`.`Directory_`, `Arguments`, `WkDir`, `Icon_`, `IconIndex`, `Hotkey`, `ShowCmd`, `Shortcut`.`Description`, `Shortcut`.`Directory_`, `Component`.`RuntimeFlags`, `Component`.`Action`, `Target`, `ComponentId`, `Feature`.`Action`, `Component`.`Installed`, `DisplayResourceDLL`, `DisplayResourceId`, `DescriptionResourceDLL`, `DescriptionResourceId` From `Shortcut`, `Feature`, `Component`, `File` WHERE `Target` = `Feature` AND `Shortcut`.`Component_` = `Component` AND `Component`.`KeyPath` = `File`.`File` AND ((`Feature`.`Action` = 1 OR `Feature`.`Action` = 2) OR (`Feature`.`Action` = 4 AND `Feature`.`Installed` = 0) OR (`Feature`.`Action` = 3 AND (`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR `Feature`.`Installed` = 4)) OR (`Feature`.`Action` = NULL AND (`Component`.`Action` = 1 OR `Component`.`Action` = 2) AND (`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR `Feature`.`Installed` = 4)))
Action start 13:55:10: CreateShortcuts.
MSI (s) (90:34) [13:55:10:638]: Doing action: FixCounters
Action ended 13:55:10: CreateShortcuts. Return value 0.
MSI (s) (90:34) [13:55:10:638]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'FixCounters'
Return value 0.
Action ended 13:55:20: INSTALL. Return value 1.
Property(S): DiskPrompt = [1]
Property(S): InstallMode = Typical
Property(S): DOTNET20SP = #2
Property(S): DOTNET35SP = #1
Property(S): DBINSTANCEREGISTRY = SHAREPOINT
Property(S): DBNAMEREGISTRY = WSS_Content
Property(S): FILESTREAMSTORENAMEREGISTRY = FilestreamProvider_1
Property(S): SCHEMASUFFIXREGISTRY = <suffix>
Property(S): WelcomeBmp = WelcomeBmp
Property(S): TRUSTSERVERCERTIFICATE = true
Property(S): SCHEDULEMAINTAINERTASK = 1
Property(S): MAINTAINERGC = GarbageCollection
Property(S): MAINTAINERREFSCAN = r
Property(S): MAINTAINERDELETE = d
Property(S): MAINTAINERORPHAN = o
Property(S): MAINTAINERCONSISTENCY = ConsistencyCheck
Property(S): MAINTAINERCONSISTENCYREPAIR = true
Property(S): OPENREADME = 1
Property(S): FilestreamPoolTranLifetimeUnit = time
Property(S): TEXTFILEVALUE = 0
Property(S): CONSOLEVALUE = 0
Property(S): DBTABLEVALUE = 0
Property(S): EVENTLOGVALUE = 4
Property(S): DBINSTANCE = jpntkyint01\sharepoint
Property(S): DBNAME = WSS_Content
Property(S): FILEGROUP = PRIMARY
Property(S): INTEGRATEDSECURITY = 1
Property(S): DBUSERNAME = username
Property(S): DBPASSWORD = **********
Property(S): FSDBINSTANCE = jpntkyint01\sharepoint
Property(S): FSDBNAME = WSS_Content
Property(S): FILESTREAMMETADATAFILEGROUP = PRIMARY
Property(S): FILESTREAMFILEGROUP = RBSFilestreamProvider
Property(S): FILESTREAMSTORENAME = FilestreamProvider_1
Property(S): SCHEMASUFFIX = <suffix>
Property(S): FILESTREAMTRANPOOLSIZE = 5
Property(S): FilestreamPoolTranLifetimeTime = 00:01:00
Property(S): FilestreamPoolTranLifetimeDays = 01
Property(S): FILESTREAMMAXPOOLSIZE = 200000
Property(S): FILESTREAMMAXSIZEINBANDWRITE = 1258290
Property(S): FILESTREAMMAXSIZEINBANDREAD = 1258290
Property(S): FILESTREAMMAXSIZEINLINEBLOB = 61140
Property(S): FILESTREAMWRITEALLOCATIONSIZE = 0
Property(S): MAINTAINERDURATION = 120
Property(S): SQLServerText1 = 0
Property(S): SQLServerVersionText3 = 0
Property(S): _IsMaintenance2 = Modify
Property(S): ModifyIcon = ModifyIco
Property(S): RepairIcon = RepairIco
Property(S): RemoveIcon = RemoveIco
Property(S): ErrorIcon = ErrorIco
Property(S): TARGETDIR = D:\
Property(S): USERNAME = Windows User
Property(S): _IsMaintenance = Reinstall
Property(S): AgreeToLicense = No
Property(S): Interrupted = 0
Property(S): SetupIcon = SetupIco
Property(S): Installed = 00:00:00
Property(S): CreateFilesNoUI = C:\Windows\system32\;D:\RBS.msi
Property(S): FixLogConfig = 4;0;0;0;0
Property(S): FixRemoteFilestreamStoreConfig = remotefilestream;C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\RemoteFilestreamProviderConfiguration.xml
Property(S): FixFilestreamStoreConfig = filestream;C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\FilestreamProviderConfiguration.xml
Property(S): RegisterProviderFile = RegisterFilestreamProvider.sql
Property(S): FILESTREAMTRANPOOLTRANLIFETIME = time 00:01:00
Property(S): IsDotNet20Or40Installed = 1
Property(S): ProgramMenuFolder.Sql = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): SAPBINOTEPAD = Notepad.exe
Property(S): MaintainerDir1025 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Maintainer\ar\
Property(S): ClientDir3082 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Client Library\es\
Property(S): FilestreamDir1025 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\ar\
Property(S): ProviderDir = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\
Property(S): Eula3082 = C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\3082\
Property(S): ProgramFiles64Folder = C:\Program Files\
Property(S): SourceDir = D:\
Property(S): VersionNT = 601
Property(S): Privileged = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {56D21E05-679B-40F2-94C1-DB0D7EB2E461}
Property(S): ProductLanguage = 1033
Property(S): ProductName = SQL Server 2008 R2 Remote Blob Store
Property(S): ProductVersion = 10.50.1600.1
Property(S): UpgradeCode = {BA2FF55A-725F-40E5-956E-D08AD0B8175B}
Property(S): ProductShortName = Remote Blob Store
Property(S): PlatformExtension = _64
Property(S): PlatformId = x64
Property(S): AppGuidRegKey = Redist_Uninstall_RegKey
Property(S): ARPPRODUCTICON = ARPIco
Property(S): ARPHELPLINK = http://www.microsoft.com/sqlserver
Property(S): PIDTemplate = 53934<````=````=````=````=`````>@@@@@
Property(S): PROMPTROLLBACKCOST = P
Property(S): INSTALLLEVEL = 100
Property(S): ALLUSERS = 1
Property(S): SuccessIcon = SuccessIco
Property(S): WarningIcon = WarningIco
Property(S): LicenseIcon = LicenseIco
Property(S): CompleteIcon = CompleteIco
Property(S): CustomIcon = CustomIco
Property(S): NewIcon = NewIco
Property(S): UpIcon = UpIco
Property(S): DialogBanner = BannerBmp
Property(S): Details = 0
Property(S): ReinstallModeText = omus
Property(S): Display_IsBitmapDlg = 1
Property(S): ProductID = none
Property(S): ISENABLEDWUSFINISHDIALOG = 1
Property(S): SQLServerVersionText1 = 0
Property(S): SQLServerVersionText2 = 0
Property(S): CA_ERRORCOUNT = 0
Property(S): CA_WARNINGCOUNT = 0
Property(S): CA_SUCCESSCOUNT = 0
Property(S): UI_SHOWCOPYRIGHT = yes
Property(S): ShowUserRegistrationDlg = 1
Property(S): ButtonTextStyle = {\ButtonTextStyle}
Property(S): DlgTextStyle = {\DlgTextStyle}
Property(S): DlgTextStyleB = {\DlgTextStyleB}
Property(S): DlgTitleStyle = {\DlgTitleStyle}
Property(S): DlgTitleStyleB = {\DlgTitleStyleB}
Property(S): FixedStyle = {\FixedStyle}
Property(S): Error_UninstallDependant = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): ProductFeaturesDefined = 1
Property(S): RBSRegistryKey = Software\Microsoft\Remote Blob Storage
Property(S): SCHEMASUFFIXVALID = 0
Property(S): EnableCustomConfigDlg = 1
Property(S): EnableCustomRemoveDlg = 1
Property(S): EnableDotNetCheck = 1
Property(S): FXAssemblyVersion = 2.0.0.0
Property(S): VSAssemblyVersion = 8.0.0.0
Property(S): EnableFeatureDlg = 1
Property(S): MaintenanceWelcomeDlg_Next = MaintenanceTypeDlg
Property(S): ReadyToRemoveDlg_Back = MaintenanceTypeDlg
Property(S): CustomerInfoDlg_Next = ReadyToInstallDlg
Property(S): CustomerInfoDlg_Back = LicenseAgreementDlg
Property(S): ReadyToInstallDlg_NotInstalled_Back = CustomerInfoDlg
Property(S): ReadyToInstallDlg_Installed_Back = MaintenanceTypeDlg
Property(S): InstallWelcomeDlg_Next = LicenseAgreementDlg
Property(S): LicenseAgreementDlg_Back = InstallWelcomeDlg
Property(S): LicenseAgreementDlg_Next = CustomerInfoDlg
Property(S): ModuleID_REDISTBASE = SQLBASE_Redist_64
Property(S): ErrorDialog = ErrorDlg
Property(S): MsiLogFileLocation = D:\rbs_install_log.txt
Property(S): PackageCode = {1AC68E73-94F1-4A01-B229-82B2F73C3326}
Property(S): ProductState = 5
Property(S): ProductToBeRegistered = 1
Property(S): CURRENTDIRECTORY = D:\
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 14660
Property(S): PRODUCTLANGUAGE = 1033
Property(S): VersionDatabase = 300
Property(S): VersionMsi = 5.00
Property(S): VersionNT64 = 601
Property(S): WindowsBuild = 7601
Property(S): ServicePackLevel = 1
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): WindowsFolder = C:\Windows\
Property(S): WindowsVolume = C:\
Property(S): System64Folder = C:\Windows\system32\
Property(S): SystemFolder = C:\Windows\SysWOW64\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\Users\MEDSVR~1\AppData\Local\Temp\
Property(S): ProgramFilesFolder = C:\Program Files (x86)\
Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Users\medsvradmin\AppData\Roaming\
Property(S): FavoritesFolder = C:\Users\medsvradmin\Favorites\
Property(S): NetHoodFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(S): PersonalFolder = C:\Users\medsvradmin\Documents\
Property(S): PrintHoodFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(S): RecentFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\Recent\
Property(S): SendToFolder = C:\Users\medsvradmin\AppData\Roaming\Microsoft\Windows\SendTo\
Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(S): CommonAppDataFolder = C:\ProgramData\
Property(S): LocalAppDataFolder = C:\Users\medsvradmin\AppData\Local\
Property(S): MyPicturesFolder = C:\Users\medsvradmin\Pictures\
Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(S): DesktopFolder = C:\Users\Public\Desktop\
Property(S): FontsFolder = C:\Windows\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): MsiAMD64 = 6
Property(S): Msix64 = 6
Property(S): Intel = 6
Property(S): PhysicalMemory = 8192
Property(S): VirtualMemory = 6311
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = medsvradmin
Property(S): UserSID = S-1-5-21-300911508-3398273753-3262312657-1000
Property(S): UserLanguageID = 1033
Property(S): ComputerName = JPNTKYINT01
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): TextInternalLeading = 3
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 13:55:20
Property(S): Date = 3/23/2015
Property(S): MsiNetAssemblySupport = 4.0.30319.34209
Property(S): MsiWin32AssemblySupport = 6.1.7601.17514
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): DATABASE = C:\Windows\Installer\6847f.msi
Property(S): OriginalDatabase = D:\RBS.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): ROOTDRIVE = D:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): DOTNETCOREPATH = 1
Property(S): SourcedirProduct = {56D21E05-679B-40F2-94C1-DB0D7EB2E461}
Property(S): SOURCEDIR = D:\
MSI (s) (90:34) [13:55:20:201]: Note: 1: 1728
MSI (s) (90:34) [13:55:20:201]: Product: SQL Server 2008 R2 Remote Blob Store -- Configuration completed successfully.
MSI (s) (90:34) [13:55:20:201]: Windows Installer reconfigured the product. Product Name: SQL Server 2008 R2 Remote Blob Store. Product Version: 10.50.1600.1. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
MSI (s) (90:34) [13:55:20:217]: Deferring clean up of packages/files, if any exist
MSI (s) (90:34) [13:55:20:217]: MainEngineThread is returning 0
MSI (s) (90:A4) [13:55:20:217]: RESTART MANAGER: Session closed.
MSI (s) (90:A4) [13:55:20:217]: No System Restore sequence number for this installation.
=== Logging stopped: 3/23/2015 13:55:20 ===
MSI (s) (90:A4) [13:55:20:217]: User policy value 'DisableRollback' is 0
MSI (s) (90:A4) [13:55:20:217]: Machine policy value 'DisableRollback' is 0
MSI (s) (90:A4) [13:55:20:217]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (90:A4) [13:55:20:217]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (90:A4) [13:55:20:217]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (90:A4) [13:55:20:217]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (90:A4) [13:55:20:217]: Restoring environment variables
MSI (s) (90:A4) [13:55:20:217]: Destroying RemoteAPI object.
MSI (s) (90:FC) [13:55:20:233]: Custom Action Manager thread ending.
MSI (c) (44:F8) [13:55:20:233]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (44:F8) [13:55:20:233]: MainEngineThread is returning 0
=== Verbose logging stopped: 3/23/2015 13:55:20 ===

I copied and pasted the strips from SSMS in another computer
CREATE
TABLE [dbo].[Taxonomy](
[fish_id] [numeric](38, 0)
IDENTITY(1,1)
NOT NULL,
[fish_order] [varchar](50)
NOT NULL,
[fish_family] [varchar](50)
NOT NULL,
[fish_genus] [varchar](50)
NOT NULL,
[fish_species] [varchar](50)
NOT NULL,
CONSTRAINT
[Taxonomy_pk] PRIMARY
KEY CLUSTERED
[fish_id] ASC
)WITH
(PAD_INDEX
= OFF,
STATISTICS_NORECOMPUTE =
OFF,
IGNORE_DUP_KEY =
OFF, ALLOW_ROW_LOCKS
= ON,
ALLOW_PAGE_LOCKS =
ON)
ON [PRIMARY]
ON [PRIMARY]

IPhoto can not find the original photo, does iPhoto copy the photo or just make a thumbnail?

Hi,
I'm scanning and putting all of my (paper) photos into my computer and then into iPhoto, tagging them, and doing all the time consuming things necessary to build a good library.
I've tried to open a few of the events and look at the photos I put in but I get an error that iPhoto can not find the original photo. When I put a photo into iPhoto does the program only make a thumbnail copy with a link to the original, or does it actually copy the photo into the library? I'm thinking the former. Because I have a Time Machine backup, a hard copy, and (presumably) a copy in iPhoto, I have been deleting the photos AFTER putting them into iPhoto. Do I need to keep the photos I put in iPhoto on my computer? Will I need to go into TM and restore them? Will I loose the information like Faces, Places, Keywords, if I do?
Thank you much,
I'm working with 9.1.2

I have exactly the same problem except my photo is named "L1000093.jpg" and it's been there for a year now, but suddenly, when I wanted to view it in it's album, ("Favorite" which has been there for a year too), it says "The photo P1010311.jpg cannot be found"!!! What the heck is going on? So I canceled, went back to the album, clicked on L1000093, clicked "show event", went over to Event, clicked "reveal in finder" and there it is, iPhoto Library/Master/blah blah blah... L1000093.jpg!
Where the hack did that P1010311.jpg came from? Sure I have that photo, but it's in a completely different event and a different album! What's is iPhoto 11 / Lion / iTunes 10.5.3(3) up to?
So I threw L1000093jpg into the trash, went into Lightroom, find the original, re-export it, load it again into iPhoto, added it again to the album (favorite), and guess what? I just did all those and the same "The bloody photo cannot be found" message popped up and when I go to finder, there it is.
This is a bug. It's been a bug since 2006 as far as I can remember. And Apple had never done a complete fix. It's an if thing!
And the most frustrating part: Althought they call this an Apple forum and you have to sign in to participate, I have never seen one Apple software guy here saying "this is what to do", just us victims helping each other and many non-Apple folks guessing to the best of their ability to comfort us.
Oh, toys are toys. I sometimes wonder if Steve had fought so hard yet the cancer in Apple actually won!

VISA Assistant can not find the instrument.

I tried to control Agilent 34970A through RS232,
but the VISA Assistant can not find the instrument,
and there is no respond when I send a command to
the instrument. I am sure that the instrument is
good, and is set to RS232 interface, the cable is
right(verified), and the parameter such as baud
rate is the same as the computer.
(I am using LabVIEW 6.1)
Can anyone give me an explain about my problem?
Thank you very much!

> "VISA Assistant" is the name of a utility that ships with Agilent VISA. I am not sure if it can work with NI-VISA.
Agilent VISA does work with NI-VISA -- provided everything is installed correctly. A user may wish to use both Agilent VISA and NI-VISA together if they have a mix of IO cards. If NI-VISA is present, then Agilent VISA should be installed in the side-by-side mode, and NI-MAX should set the Passport to On. Then LabVIEW will see all the Agilent cards, and Agilent VISA Assistant will see all the NI-Cards. (The last time I tried this though, NI-MAX didn't see the Agilent cards.)
What was not mentioned in the original question is what VISA configuration is being used. If more specifics are provided a more specific answer can be given.
[email protected]

How can i find the printing program?

hi
i have sap script how can i find the printing program ?
ami

ami bardogo wrote:
hi
what is the different between the commands 'break' and 'break-point'
thanks,
ami
h2 Breakpoints h2
Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
Directly set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statements
The Debugger stops the program immediately before the specified statement is executed.
Breakpoints
at subroutines
The Debugger stops the program immediately before the specified subroutine is called.
Breakpoints at function modules
The Debugger stops the program immediately before the specified function module is called.
Breakpoints at methods
The Debugger stops the program immediately before the specified method is called.
Breakpoints at exceptions and system exceptions
The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
·        You do not have to change the program code.
·        You can set them even when the program is locked by another programmer.
·        You can define a counter that only activates the breakpoint after it has been reached.
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
For further information on special breakpoints, refer to:
Breakpoints at Statements
Breakpoints at Subroutines
Breakpoints at Function Module Calls
Breakpoints at Methods
Breakpoints at System Exceptions
h2 page break h2
WINDOW TYPES
When defining a layout set window, you must select a window type for the window. You can choose between three types:
Constant windows (CONST)
Variable windows (VAR)
Main windows (MAIN)
CONSTANT WINDOW
A window of type CONST has the same contents and size on all layout set pages, on which a corresponding page window is defined. This allows the processing of the window contents to be optimized internally.
Page windows whose allocated window is of type CONST must have the same size throughout the layout set. If a window of type CONST is full, all remaining text the application program wants to output in this window, is lost. Constant windows do not trigger a page break. In other words: all text exceeding the window size is simply truncated.
VARIABLE WINDOW
The contents of variable windows is processed again for each page, on which the window appears. The system outputs only as much text as fits into the window. Text exceeding the window size is truncated; the system does not trigger a page break. Unlike constant windows, the page windows declared as variable windows may have different sizes on different layout set pages.
As far as the processing of the window contents is concerned, the system currently treats constant and variable windows alike. The only difference is that constant windows have the same size throughout the layout set.
MAIN WINDOW
Each layout set must have one window of type MAIN. Such a window is called the main window of the layout set. For SAPscript layout sets, the main window has a central meaning:
It controls the page break.
It contains the text body that may cover several pages.
It allows to fix text elements at the upper and lower margins of the allocated page window (for example, for column headings).
As soon as a window of type MAIN is full, SAPscript automatically triggers a page break and continues to output the remaining text in the main window of the subsequent page. Page windows of type MAIN have the same width throughout the layout set. The SAPscript composer thus avoids reformatting of the text after each page break.
If a page does not have a main window, the system implicitly processes all other windows of the page and continues with the subsequent page. This page must not call itself as subsequent page (recursive call), since this would produce an endless loop. In such a case, SAPscript terminates the output after three subsequent pages.
HOW THE COMPOSER WORKS
The composer or layout set processor is the central formatting module for the print output. It prepares the texts for the different output devices by using the allocated styles or layout sets.
Processing a layout set happens in a certain order. You must know some facts concerning the different window types, the setting of subsequent pages, or the dynamic control from within the print program.
Page control in layout sets
Define subsequent page statically
Define subsequent page dynamically
Format a layout set page
PAGE CONTROL IN LAYOUT SETS
SAPscript automatically triggers a page break as soon as the main window of one page is full. To be able to execute the page break, the system must know on which subsequent page to continue outputting the text. You can specify the subsequent page either statically when defining the layout set, or you can set the subsequent page dynamically during layout set output.
If the subsequent page is not specified, SAPscript automatically terminates printing, thereby ignoring any other output statements of the application program.
DEFINE SUBSEQUENT PAGE STATICALLY
You define the subsequent page statically with the layout set maintenance transaction. First, specify the start page in the layout set header. The system automatically calls this page whenever the layout set is started. With this page, or, more correctly, with the page window of this page, the text output starts. For each page, specify the subsequent page in the page definition. After a page break, the system continues text output on the subsequent page defined for the last page. By specifying start page and subsequent pages, you can define a page sequence.
DEFINE SUBSEQUENT PAGE DYNAMICALLY
The page sequence set in the layout set definition can be changed by the application program dynamically at runtime. If you want the layout set to start with a page other than the one defined in the layout set header, specify the desired start page using the parameter STARTPAGE when you call the function module START_FORM. However, this new start page is valid only for the current call of the function module.
If you want to break to a subsequent page other than the one specified in the page definition, use the control statement NEW-PAGE to set the name of the new page.
NEW-PAGE .
NEW-PAGE ends the output on the current page. The new subsequent page is only valid for the current call of the control statement. You can either include the control statement explicitly into the text of a text element or pass it to the layout set output using the function module CONTROL_FORM.
FORMAT LAYOUT SET PAGE
The process of formatting the output is controlled by the text contents in the BODY area of the main window. If the main window is completely filled, or if the control statement NEW-PAGE appears in the main window, the system executes a page break. Only at this point in time the system formats the contents of the windows of the other types and replaces the variables with the current values.
For each other window, the system first outputs the default text element, if it exists. Then it processes and formats the list of the active text elements of this window, which you set using the function module WRITE_FORM with the parameter FUNCTION (SET, APPEND, DELETE). Any text that does not fit into the page window is truncated.
As a consequence to this processing order of the composer, the reservation of space for the TOP and BOTTOM areas must be made beforehand. If the BODY area of the main window already contains text, a new text output to the TOP area does not appear on the current page but on the subsequent page in the TOP area. The same applies for the BOTTOM area. If the BODY area is filled to such an extend that the new BOTTOM text no longer fits into the current main window, this text appears on the subsequent page in the BOTTOM area.
A frequent error in application programs is that for the subsequent page (for example, NEXT) of a layout set no main window is defined. If the formatted text of the previous page did not fit into the corresponding main window , the composer searches the subsequent pages for a main window to output the text remainder. However, if the subsequent page of NEXT is NEXT again, the composer encounters an endless loop.
To be able to create correct page breaks in longer text, you should define a main window on each layout set page.
LAYOUT SET CONTROL
To output SAPscript layout sets, in the print program you must always start the output with OPEN_FORM and end it with CLOSE_FORM. The function module OPEN_FORM initializes the SAPscript composer and opens the specified layout set for subsequent output. The system combines all output for this layout set up to the CLOSE_FORM to one print request. If CLOSE_FORM is missing, nothing will be printed.
To output data in a layout set, you must use the SAPscript function modules WRITE_FORM, WRITE_FORM_LINES, and CONTROL_FORM. You can use these function modules any number of times in any order between opening and closing a layout set.
You cannot use the ABAP/4 statement WRITE to write output to a SAPscript layout set.
Several print requests
Start a layout set again
Switch layout sets
Find layout sets
SEVERAL PRINT REQUESTS
Within one transaction, you can open and close several layout sets using OPEN_FORM and CLOSE_FORM, however not simultaneously. You can use parameters in the OPEN_FORM to control whether the output is stored in the same print request. But also the SAP spool decides, depending on several plausibility checks, whether new output is appended to an existing print request or whether to create a new print request anyway.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
You cannot combine ABAP/4 list output and SAPscript output in one print request.
START A LAYOUT SET AGAIN
Usually a print program does not print only one urging letter or one account statement, but several layout sets for different customers. To have the output for each customer begin with the start page of the layout set, you must start the current layout set again and again.
To start a layout set again, you must first end the current layout set and then open the layout set again. Within one print request, first call the function module END_FORM. It executes the final processing for the current layout set. Then start the layout set again using START_FORM. Output then begins again on the start page of the desired layout set.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION CLOSE_FORM
If you use START_FORM and END_FORM, you must not specify a layout set for OPEN_FORM. However, in this case you can use the SAPscript output functions only after opening a layout set with START_FORM.

Mac mini can not find the NAS

In my network I have a Mac mini, AirPort Extreme base station and a Netgear ReadyNAS Duo v2. Everything is connected by cable. The problem is that the Mac mini can not find the NAS. Mac mini is looking for wirelessly connected devices, type TimeCapsule. How do I get my Mac mini to find the NAS and set the NAS as a source of data storage?

I have a ReadyNAS and use it as a Time Machine destination with no problems, even over WiFi. The ReadyNAS and Mac are both on the same LAN (even though the Mac is on WiFi), please check to see if your WiFi is on a different LAN to the Ethernet side of things, I have my Airport set to bridging mode so both sides of the AirPort count as the same LAN.
Next you need to check you have actually configured Time Machine in the ReadyNAS, as shipped it is initially turned off. You need to go to the ReadyNAS web management interface (FrontView) and then click on Backup on the left, and then select Time Machine. You also need to make sure Bonjour is enabled for the ReadyNAS, this is accessed by clicking on Services on the left and then selecting Discovery Services, make sure all the Bonjour options are ticked on.

Error!! Can not find the delivery details for the delivery Id :

hi all,
I have a report which i need to burst in seven different reports wherein my delivery key is column "emp_id". Now when i schedule the report to burst then the report completes with a warning. I see that there are various delivery cycles for the report and for one of the cycles i get the following message
Error!! Can not find the delivery details for the delivery Id :
hence, what happens due to this is, even there are successful deliveries for other delivery ids but then i get only two rows of data in each of the seven bursted ouput xls files. wheareas the data runs in thousands of rows for each cycle.
Hence whats happening is, that due to error /warning in one of the delivery cycles other reports are also not showing data.
I am not sure whats causing the issue and why i am not getting complete bursted files out.
Please suggest
Thanks
Ronny

I guess, you are in 10.1.3.3.2 :),
in the latest release 10.1.3.4.1, there are more enhancement wrto bursting and performance i believe.
check th release notes
can you send me the xml and bursting query you have, i can try simulating in my local.

OWB 11gR2 - Internal ERROR: Can not find the ACL containter

OWB 11gR2 - Internal ERROR: Can not find the ACL containter
=======================================
I am using OWB 11gR2 (11.2.0.1) on Win XP 32 bit. I have 3.23 GB RAM. OWB design center is ver slow on my desktop. We have our OWB repository is on Unix server.
We applied the patch 10270220.
We are getting
Internal ERROR: Can not find the ACL containter for object:CMPPhysicalMap@19654/id=104020/owningFCO=104020/proxyFor=(CMPPhysicalMapGen@19f99ae/id=104020/stname=null/pname=MAPPING_1/lname=MAPPING_1/status=POSTED/committed=true/persistent=true/propsLoaded=true)
What is happening here?
Thanks in helping.

We have a map with 3 sources and 1 target. The 3 sources pass through Joiner then Expression then Target.
We are getting this error, during deployment. It shows compling for awhile, then through this error.
Here is the piece from detail window:
===========
at oracle.wh.repos.pdl.security.SecurityPolicyManager.getAccessCharMapOfPrivilegeOwner(SecurityPolicyManager.java:174)
     at oracle.wh.repos.impl.foundation.CMPElement.getAccessCharMapOfPrivilegeOwner(CMPElement.java:2806)
     at oracle.wh.repos.pdl.security.OWBSecurityImpl.hasPrivilege(OWBSecurityImpl.java:914)
     at oracle.wh.repos.pdl.security.OWBSecurityImpl.internalSecurityCheck(OWBSecurityImpl.java:1542)
     at oracle.wh.repos.pdl.security.OWBSecurityImpl.securityCheck(OWBSecurityImpl.java:694)
     at oracle.wh.repos.pdl.security.SecurityModuleImpl.securityCheck(SecurityModuleImpl.java:959)
     at oracle.wh.repos.pdl.security.SecurityModuleImpl.securityCheck(SecurityModuleImpl.java:924)
     at oracle.wh.repos.pdl.dispatcher.EventDispatcherImpl.beforeReadObject(EventDispatcherImpl.java:824)
     at oracle.wh.repos.pdl.foundation.OWBRoot.beforeRead(OWBRoot.java:1785)
     at oracle.wh.repos.owbGen.CMPStringPropertyValueGen.getValue(CMPStringPropertyValueGen.java:217)
     at oracle.wh.repos.impl.properties.CMPStringPropertyValue.getValue(CMPStringPropertyValue.java:117)
     at oracle.wh.repos.impl.extended.PropertyFactory.getStringValue(PropertyFactory.java:440)
     at oracle.wh.repos.impl.extended.CMPWBPrimitiveProperty.rawStringValue(CMPWBPrimitiveProperty.java:260)
     at oracle.wh.repos.sdk.mapping.WBMapHelper.getStringProperty(WBMapHelper.java:716)
     at oracle.wh.repos.sdk.mapping.WBMapHelper.getStringProperty(WBMapHelper.java:733)
     at oracle.wh.repos.sdk.mapping.WBMapHelper.getReferencedLocations(WBMapHelper.java:1361)
     at oracle.wh.service.impl.runtime.EnvironmentUtils.getReferencedLocations(EnvironmentUtils.java:284)
     at oracle.wh.service.impl.runtime.EnvironmentUtils.getReferencedLocations(EnvironmentUtils.java:141)
     at oracle.wh.service.impl.runtime.EnvironmentUtils.getReferencedLocations(EnvironmentUtils.java:135)
     at oracle.wh.service.impl.runtime.RuntimePlatformServiceImpl.getReferencedLocations(RuntimePlatformServiceImpl.java:1238)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandUtil.addConnectorLocations(WHRuntimeCommandUtil.java:477)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.getSingleDeployLocations(WHRuntimeCommandGenerateDeploy.java:3408)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.getLocationsAndNewConnectors(WHRuntimeCommandGenerateDeploy.java:3517)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.doPreDeploymentActions(WHRuntimeCommandGenerateDeploy.java:3224)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy._internalDeploy(WHRuntimeCommandGenerateDeploy.java:2420)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandGenerateDeploy.doDeploymentAsynch(WHRuntimeCommandGenerateDeploy.java:2117)
     at oracle.wh.ui.runtime.application.WHRuntimeCommandHandler$1.construct(WHRuntimeCommandHandler.java:1005)
     at oracle.wh.ui.runtime.SwingWorker$2.run(SwingWorker.java:124)
     at java.lang.Thread.run(Thread.java:595)
===========
Did anyone receive such errors?

Warnings in FileReference - can not find the cause

I'm trying to make a loader of a few photos (use FileReference). I get the warnings, but I do not know the reason for their appearance.
warning: unable to bind to property 'fr' on class 'Object' (class is not an IEventDispatcher)
warning: unable to bind to property 'name' on class 'flash.net::FileReference'
warning: unable to bind to property 'data' on class 'flash.net::FileReference'
warning: unable to bind to property 'fr' on class 'Object' (class is not an IEventDispatcher)
warning: unable to bind to property 'name' on class 'flash.net::FileReference'
warning: unable to bind to property 'data' on class 'flash.net::FileReference'
CODE:
import mx.events.CollectionEvent;
import flash.net.FileReferenceList;
import mx.collections.ArrayCollection;
[Bindable]
private var photos:ArrayCollection = new ArrayCollection;
private var frList:FileReferenceList = new FileReferenceList;
private function init():void
photos.addEventListener(CollectionEvent.COLLECTION_CHANGE,function():void
startUploadButton.enabled = (photos.length>0);
clearPhotosButton.enabled = (photos.length>0);
frList.addEventListener(Event.SELECT,addPhotos);
private function selectPhotos():void
var fileFilter:FileFilter = new FileFilter("Images jpeg","*.jpg;*.jpeg");
frList.browse([fileFilter]);
private function addPhotos(e:Event):void
for (var i:uint = 0; i < frList.fileList.length; i++)
var elem:Object = new Object;
elem.fr = FileReference(frList.fileList[i]);
elem.fr.load();
elem.fr.addEventListener(Event.COMPLETE,refreshThumb);
photos.addItem(elem);
private function refreshThumb(e:Event):void
photosList.invalidateList();
public function clearPhoto(data:Object):void
photos.removeItemAt(photos.getItemIndex(data));
photosList.invalidateList();
private function startUpload():void
photosProgressContainer.visible = true;
var request:URLRequest = new URLRequest();
request.url = "http://localhost/tempLoader-debug/upload.php";
var fr:FileReference = photos.getItemAt(0).fr;
fr.cancel();
fr.addEventListener(ProgressEvent.PROGRESS,uploadProgress);
fr.addEventListener(DataEvent.UPLOAD_COMPLETE_DATA,uploadComplete);
fr.upload(request);
private function uploadProgress(e:ProgressEvent):void
photosProgress.setProgress(e.bytesLoaded,e.bytesTotal);
private function uploadComplete(e:DataEvent):void
photos.removeItemAt(0);
photosList.invalidateList();
if (photos.length > 0)
startUpload();
else
photosProgressContainer.visible = false;

In my opinion this is the line that is causing you the warning:
<mx:Image source="{data.fr.data}" maxWidth="100" maxHeight="75"
horizontalAlign="center" verticalAlign="middle" />
That means that data should be a custom binable object and fr should be another
custom bindable object.
like
public class BindableData
    public var fr:BindableData2;
public class BindableData2
    public var data:String;
I am not sure though what you are trying to do though, but I assume you try top
load an image from your disk. This link will help you:
view source enabled...
http://www.everythingflex.com/flex3/flexcampItaly/
the blog post ...
http://blog.everythingflex.com/2009/09/08/flexcamp-presentation-filereference-load-part-1- of-3/
C
From: Astraport2012 <[email protected]>
To: Ursica Claudiu <[email protected]>
Sent: Sun, October 3, 2010 3:07:57 PM
Subject: Re: Warnings in FileReference - can not find the cause
I found the solution to the first part of the warning. Only need to modify the
object as ObjectProxy
public var elem:ObjectProxy = new ObjectProxy;
But with the second part is still a problem (warning: unable to bind to property
'name' on class 'flash.net::FileReference'
warning: unable to bind to property 'data' on class 'flash.net::FileReference').
I do not fully describe the problem in the first message. The main application
calls the component and passes it parameters. They cause errors.
It is this component photoThumb.mxml:
<?xml version="1.0" encoding="utf-8"?>
   width="120" height="110"
   backgroundColor="#FFFFFF" backgroundAlpha="0"
   rollOver="{controls.visible=true;}" rollOut="{controls.visible=false;}">
<mx:Image source="@Embed('t1.png')" width="100%" height="100%" alpha="0"
horizontalAlign="center" verticalAlign="middle"/>
<mx:VBox width="100%" height="90" y="5" horizontalAlign="center" >
<mx:Image source="{data.fr.data}" maxWidth="100" maxHeight="75"
horizontalAlign="center" verticalAlign="middle" />
</mx:VBox>
<mx:Label text="{data.fr.name}" width="118" truncateToFit="false" bottom="0"
textAlign="center" />
<mx:VBox id="controls" visible="false" y="65" right="10" horizontalAlign="right"
>
<mx:Button label="X" click="parentDocument.clearPhoto(data)" fontSize="6"
width="30" height="15" />
</mx:VBox>
</mx:Canvas

Nternal ERROR: Can not find the ACL containter for object ...

We are using OWB 10.2.0.3. We tried to introduce two basic roles to prevent user A from accessing certain parts of our project. Somehow (I cannot really say how) we ended up in the error message below whenever we want to modify the security properties of an object.
Neither in metalink nor in the oracle forums I could find any hint about that error.
Can anyone help??
Thanks in advance, Maren
Internal ERROR: Can not find the ACL containter for object:CMPMap@1ba11bc/id=2023180/owningFCO=2023180/proxyFor=(CMPMapGen@1a4d5c6/id=2023180/stname=CMPBatchMap/pname=LOAD_XML/lname=LOAD_XML/status=CLEAN/committed=true/persistent=true/propsLoaded=false)
Internal ERROR: Can not find the ACL containter for object:CMPMap@1ba11bc/id=2023180/owningFCO=2023180/proxyFor=(CMPMapGen@1a4d5c6/id=2023180/stname=CMPBatchMap/pname=LOAD_XML/lname=LOAD_XML/status=CLEAN/committed=true/persistent=true/propsLoaded=false)
     at oracle.wh.repos.pdl.security.SecurityPolicyManager.getAccessCharMapOfPrivilegeOwner(SecurityPolicyManager.java:166)
     at oracle.wh.repos.impl.foundation.CMPElement.getAccessCharMapOfPrivilegeOwner(CMPElement.java:2743)
     at oracle.wh.repos.pdl.security.OWBSecurityImpl.hasPrivilege(OWBSecurityImpl.java:820)
     at oracle.wh.repos.pdl.security.OWBSecurityImpl.internalSecurityCheck(OWBSecurityImpl.java:1449)
     at oracle.wh.repos.pdl.security.OWBSecurityImpl.securityCheck(OWBSecurityImpl.java:649)
     at oracle.wh.repos.pdl.security.SecurityModuleImpl.securityCheck(SecurityModuleImpl.java:660)
     at oracle.wh.repos.pdl.security.SecurityModuleImpl.securityCheck(SecurityModuleImpl.java:623)
     at oracle.wh.ui.common.WhSecurityHelper.securityCheck(WhSecurityHelper.java:112)
     at oracle.wh.ui.console.commands.EditObjectCmd.performAction(EditObjectCmd.java:107)
     at oracle.wh.ui.console.commands.TreeMenuHandler$1.run(TreeMenuHandler.java:188)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:189)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:478)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

Hi Maren
Like you I get this error and do not know what steps caused it.In my scenario I have some mappings that give the error and some that do not - the repository user gets the error but the repository owner does not.
Thinking back over the last number of months (as this project contains 7-8 months od work - we do have exports of the project) I think the ones giving the error are those that perhaps were copied from another to start the coding but I cannot be sure.
I have read the metalink note mentioned above as well as the the queries posted by Oleg and yourself. The queries posted are slightly different, one has a where clause
fco.classname = 'CMPACLContainer' (Maren's)
and the other
fco.classname='CMPMap' (Oleg's).
Was this intentional Maren on your behalf for your problem to be fixed?
We are using 10.2.0.3.33 OWB client and 10.2.0.3.0 OWB repository.
Thanks
Edwin

Can not find the mixer program "sndvol32"

Similar Messages

Maybe you are looking for