Problems since upgrading to Leopard

I have a Powermac G5 2.0 dual, 12 gig ram, 10.5.4. Since I upgraded to 10.5.4 and installed an eSATA for the time machine backup, I've had the oddest problems. It takes between 5 and 10 minutes for the computer to start up and get past the blue screen to the log in screen. Then time machine is no where to be found, despite the "my book" 1 terabyte eSATA drive appearing to be on. I then turn on the drive and it seems to speed things up a bit.
I ran the disk utility, which took forever to operate. No errors or problems were found.
I'm a bit lost. Leopard has been a frustrating upgrade so far and I'm looking for some possible solutions. Should I just take the eSata out for the moment and see what happens without it?
Suggestions?
Thanks

I disconnected the eSATA and the system started in normal time. I've since reconnected the eSATA and it is back to being very slow to recognize the MyBook 1terabyte drive. Any suggestions on what could be causing the eSATA to be so slow in being recognized? The initial backup to Time Machine was super fast once it got started and the set up seems to be speedy once the drive is recognized. It is just taking between 5 and 10 minutes to recognize the eSATA.
Suggestions?
Thanks

Similar Messages

MB Pro, with Tiger, which has since upgraded to Leopard - Install Discs?

My MacBook Pro had originally been installed with Tiger. I have since upgraded to Leopard.
Should I need to boot from my install discs, which install disc do I use? Will my Tiger install discs work with Leopard, or should I use my Leopard disc (retail version)?
Thank you!

{quote:title=Kappy wrote:}
Actually you would be better to install Leopard directly. You can reinstall pre-bundled software separately without installing Tiger. An Erase and Install of Leopard would be preferable to installing Tiger then upgrading to Leopard. Less chance of a problem.
Hi Kappy,
Some, at least, of the late 2007 MBP C2D 2.2 and 2.4 GHz MBPs (mine included) actually came with Tiger Installed, but with a "drop in" copy of Leopard enclosed in the box. From memory the version of Leopard included will only install if the original software is in place. (I'm not 100% certain of this, but I'll check) Not sure what Trisha's situation is, of course, but worth bearing in mind as a possible issue.
Cheers
Rod

Since upgrading to Leopard I cannot iSync to my Nokia 6233

Since upgrading to Leopard I cannot iSync to my Nokia 6233 via bluetooth (I never did it by USB). The devices are paired and I can transfer files via Bluetooth so the basic setup is there. I have installed the Nova Media phone plugins for isync and my 6233 appears on my isynch bar and allows me to chose what to sync but when I click sync it cannot connect. (I have also been unable to use launchtonet from Nova Media since the upgrade. When I try to use it I get a message that no devices were found within reach.) Something is out of kilter - anyone got a suggestion? thanks a lot, JJ

Hello,
I have the same Nokia 6233 and the following way solved the problem.
1. Go to /Applications -> iSync.app -> Contents -> PlugIns -> ApplePhoneConduit.syncdevice -> Contents -> PlugIns -> PhoneModelsSync.phoneplugin -> Contents -> Resources. (From Finder, use Shift-Command-G, for Go to Folder; or Control-click iSync in Applications.)
2. Open MetaClasses.plist in a text editor.
3. Search for <key>com.nokia.6230</key>. Then find the end of the script for the 6230 phone - the </dict> tag just before the next phone's <key> tag.
4. Copy the following script and paste it between the </dict> tag for the 6230 and the next phone's <key> tag:
<key>com.nokia.6234</key>
<dict>
<key>Identification</key>
<dict>
<key>com.apple.cgmi+cgmm</key>
<string>Nokia+Nokia 6234</string>
</dict>
<key>InheritsFrom</key>
<array>
<string>family.com.nokia.series40.3rdEd.bus.bt</string>
</array>
<key>Services</key>
<array>
<dict>
<key>ServiceName</key>
<string>com.apple.model</string>
<key>ServiceProperties</key>
<dict>
<key>ModelIcon</key>
<string>NOK6234.tiff</string>
<key>ModelName</key>
<string>6234</string>
</dict>
</dict>
</array>
</dict>
5. If you have a Nokia 6233, change all the references to 6233 to 6234.
6. Save and close the MetaClasses.plist file.
7. In the same folder, duplicate the file NOK6230.tiff. Change the filename to NOK6234.tiff (or NOK6233.tiff if that is your phone). This file is the image of your phone which appears in iSync - if you want an accurate pic of the 6233/6234, find one and save it as a 60x60 transparent .tiff file).
8. Open Bluetooth Preferences. Delete any existing pairing for your Nokia 6233 or 6234 phone.
9. Create a new pairing for your phone.
10. Open iSync and you should now be able to sync your phone:)
If it works just copy the MetaClasses.plist file and save it anywhere. For the next updates You just have to copy it into the folder in iSync. This helps You saving time.
If You want to use my MetaClasses.plist, You may send me Your Email-adress. Then I will send it to You.
Good luck

Since upgrading to Leopard, can't check for software updates or iTunes stor

since upgrading to Leopard, i can't get software upgrades. I get error messages "software update can't connect to the update server. make sure you're connected to the internet, then try again. software update can't check for updates because of a network problem." My network connections are fine.
Also get "itunes could not connect to the itunes store. the network connection was refused. make sure your network settings are correct and your network connection is active, then try again." when I try to go to itunes store. Again, my network connections are fine.
Any ideas?

the solution is to use Little Snitch Configuration.app, which monitors online activity and gives option to allow/deny access of a given program.

'Bluetooth not available' error message since upgrading to Leopard

Hi, I regularly seem to get a 'Bluetooth not available' error message since upgrading to Leopard, any ideas why, have to reboot to shake it.
cheers
Simon

I solved the same issue by resetting the SMC. With the computer off, remove the battery and press and hold the power button for 5 seconds. Then reinstall the battery and restart. I haven't had any bluetooth issues since.

Ipad3 problems since upgrading to ios8n

Is anyone else experiencing these problems since upgrading to iOS 8?
- Need to touch screen several times for a nornal one touch action (note: Screen size/position changes a bit after each successive try.)
- keyboard response slow at times and at times freezes
- screen content/image has expanded slightly but enought to put some perimeter icons and controls outside/off the screen.
Are there fixes?
ios7 worked beautifully!!! Why won't Apple allow their currently loyal ( but frustrated) clients to revert back to ios7?

Hi Go to settings Restore back, to Factory, settings After Restore use same Apple ID & password, then you will get all your apps & data, back. This will get rid of any bugs. I do this every 2 months, or so on iPhone & iPad. Cheers Brian

Any Bluetooth audio problems since upgrading to ICS?

Hi.
Was wondering if anyone has had any Bluetooth audio problems since upgrading to ICS? In particular, have you had any stuttering and/or pauses in streaming since the upgrade?
I use a MW600 with my phone and I get stuttering and pauses every few minutes between the phone and the MW600 which is very annoying - to the point where I can't reliably use the phone for audio any more.
Thanks
Savcom

Sorry but it seems to be a problem some users are experiencing. It's already been reported so hopefully there will be a fix for this soon.
- Community Manager Sony Xperia Support Forum
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page.

Problems since upgrading to Mavericks

I am experiencing problems with CC applications since upgrading to Mavericks. Mostly Screen and display issues.
In Photoshop, the top menu bar where the red, yellow , green window buttons normally sit has disappeared and it seems I cannot drag the window down to reveal (if that is the problem)
In Indesign, The program opens but I cannot see any workspace at all, even when I open an existing ID file.
Premiere Pro, Bridge, appear to work OK
After effects and Muse indicated both required upgrades, yet the CC application Manager does not indicate any upgrades required or available.
I have not tried other apps.
Is anyone else experiencing problems since upgrading to Mavericks and if so, does anyone know if Adobe are working on fixes?

I upgraded to Mavericks on two computers and have display problems too! I have CC on one Macbook Pro (2011) and CS6 on another (2012) and I'm now almost positive my display problems are triggered by InDesign. I don't have to be doing anything special, and I don't have to be working in InDesign at the time, but InDesign has to be open and I get things like this:
Once it turns magenta or green, that's when I have to boot the system. I can still work with the glitchy display before it turns colors and if I'm still able to quit InDesign while it's glitching, the display goes back to normal. Same on both computers and the 2011 one has a new logic board in it.
At first I thought it had something to do with connecting my hard drive or my external display, but the display issues happened with both computers with nothing hooked up. Those are ruled out now. I took my 2012 computer to Apple and they told me it was a software issue and all my hardware is ok. Obviously they didn't fix the software issue because it's still happening.
This is not normal and needs to be fixed soon!

Please help - computer is crashing & freezing ever since upgrade to Leopard

Ever since upgrading to Leopard, my computer has been crashing a lot more. Sometimes it just freezes up. Most recently, I got the gray screen with a bunch of different languages telling me to restart using the power button. Here is the crash report. Can anyone tell me what's going on, and if there's anything I can do to help?
Thanks!
Tue Mar 24 13:00:49 2009
panic(cpu 0 caller 0x001A9C68): Kernel trap at 0x0040de14, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000002c0, CR3: 0x0108a000, CR4: 0x00000660
EAX: 0x06745c00, EBX: 0x2e583bf0, ECX: 0x06745ccc, EDX: 0x00000000
CR2: 0x000002c0, EBP: 0x2e583bd8, ESI: 0x04866d00, EDI: 0x06745c00
EFL: 0x00010206, EIP: 0x0040de14, CS: 0x00000008, DS: 0x01880010
Error code: 0x00000000
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x2e5839e8 : 0x12b4f3 (0x45b13c 0x2e583a1c 0x1335e4 0x0)
0x2e583a38 : 0x1a9c68 (0x464700 0x40de14 0xe 0x463eb0)
0x2e583b18 : 0x1a038d (0x2e583b30 0xb6dcfb0 0x2e583bd8 0x40de14)
0x2e583b28 : 0x40de14 (0xe 0x48 0x2e580010 0x140010)
0x2e583bd8 : 0x7474b9 (0x6745c00 0x0 0x0 0x0)
0x2e583c48 : 0x747547 (0x6745c00 0x4866d00 0x9a00780 0x19eb5b)
0x2e583c68 : 0x5db609 (0x4866d00 0x4 0x46 0x136b31)
0x2e583cc8 : 0x5db679 (0x5a30600 0x4866d00 0x2 0x2)
0x2e583d08 : 0x34773463 (0x5a30600 0x4866d00 0x2 0x2)
0x2e583d28 : 0x60b211 (0x5a30600 0x4866d00 0xe0004051 0x1f)
0x2e583d98 : 0x85b117 (0x3c29000 0x3d88900 0xe0004051 0x1f)
0x2e583e38 : 0x85c047 (0x3c29000 0x3e79488 0xe0004051 0x0)
0x2e583e88 : 0x85c1b4 (0x3c29000 0x3e785c0 0xc954252c 0x7f33)
0x2e583ec8 : 0x6078f7 (0x3c29000 0x3e8 0x53f69c 0x3e10a40)
0x2e583f28 : 0x424cb8 (0x3c29000 0x3d68b00 0x53f0c0 0x1)
0x2e583f78 : 0x13eed2 (0x3d68b00 0x3d68919 0x0 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBMassStorageClass(2.0.4)@0x34772000->0x3477bfff
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.0.5)@0x5d5000
dependency: com.apple.iokit.IOUSBFamily(3.2.7)@0x606000
dependency: com.apple.iokit.IOStorageFamily(1.5.5)@0x72d000
com.apple.iokit.SCSITaskUserClient(2.0.5)@0x745000->0x74afff
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.0.5)@0x5d5000
dependency: com.apple.iokit.IOStorageFamily(1.5.5)@0x72d000
com.apple.iokit.IOSCSIArchitectureModelFamily(2.0.5)@0x5d5000->0x5edfff
com.apple.driver.AppleUSBEHCI(3.2.5)@0x851000->0x862fff
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x636000
dependency: com.apple.iokit.IOUSBFamily(3.2.7)@0x606000
com.apple.iokit.IOUSBFamily(3.2.7)@0x606000->0x62efff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBookPro2,2 (Mac-F42187C8)

I'd suggest doing this:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Problems since upgrading to v9.10

Has anyone else encountered problems since upgrading to v9.10?
Firstly there appears to be an issue with OLT no longer working in Firefox (3.6) as the "Build Scenarios" lists (select scripts) don't populate. Fortunately it still works in IE7, so I can at least revert to that.
Apart from that, what's more of a problem is that I've found some previously working scripts are no longer working in OLT (but I haven't yet found a pattern).
e.g. 1) One webservices script for product 'A' works, yet another for the same product comes back with "Orphaned agent" and "Failed to load script class for script X".
e.g. 2) A similar set of scripts for a different webservice 'B' also has one working and the other with the same errors generated.
e.g. 3) I have some web scripts that work, but others come back with the errors shown.
I have also noticed that if I attempt to run multiple scripts e.g. load a previously working scenario containing 12 scripts, none of the scripts runs (as the agent has failed to start because of at least one of the scripts). The same is true if I try and run a single working script with a single non-working script; both fail with the message from the non-working script (both would be using the same agent).
So far I have only tried converting a (new copy of a) single script to the v9.10 format but that didn't seem to make a difference. Pre-v9.10 scripts should still work in OLTv9.10 though; the conversion shouldn't be necessary.
I have tried the usual things (re-starting the services and even the OracleXE database). Any suggestions?

I too have FF3.6.3 but after signing in, I get the Build Scenarios page displayed but the "Select scripts & user-defined profiles" box with "Path: Scripts Only" list has nothing in it. Changing to "Scripts and Directories" makes no difference, still nothing is shown in the list. The repository should have multiple directories with multiple scripts (as shown when I try the same thing in IE7).
I now suspect this too may be down to some problem during the upgrade of the DB from v9.01.1 to v9.10 the odd thing with the script failures is the error doesn't seem to indicate anything wrong with the script itself; just that the agent failed to load the script. You get OLT Server Warnings that say "Stopped Autopilot because of error on agent "[name]" and the VU Grid shows my (single) VU with error "Failed to load script class for script [name]".
One particularly odd thing is that if I try adding 2 scripts in the same batch (a working and non-working one) with a delay between them the following happens:
1) VU1 with working script starts and completes OK (total time around 48s)
2) VU2 starts after delay (120s) but immediately comes back with the OLT Server Warning.
3) *BOTH* VUs on the VU Grid now show the same error about the agent (despite the 1st VU having completed sucessfully).
The agent seems to run happily with a working script until it is asked to load another (non-working) script which then kills the agent?
Here's the relevant section from the databaseConfig.log from when the upgrade was installed, as I suspect this is where the problem started:
+[Apr 16 10:21:42] INFO (SchemaUpgrader.java:43) - Starting upgrade for schema Oats+
+[Apr 16 10:21:48] INFO (SchemaUpgrader.java:50) - Schema Oats is version 9.01.1+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script db_users.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script init_ats_dbs.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script oats.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script oats_template_data.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script olt.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script olt_sample_data.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script olt_template_data.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script otm.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script otm_sample_data.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script otm_template_data.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4b_to_v4c Oracle.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4b_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4d Access.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4d SqlSrv.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4e Access.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4e Oracle.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4e SqlSrv.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4f Access.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4f SqlSrv.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4e Access.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4e Oracle.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4e SqlSrv.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4f Access.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4f SqlSrv.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4e_to_v4f Access.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4e_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script Update v4e_to_v4f SqlSrv.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script upgrade-oats.9.01.1.sql does not match the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:71) - Script upgrade-oats.9.10.1.sql matches the filter+
+[Apr 16 10:21:48] DEBUG (SchemaUpgrader.java:82) - Script upgrade-olt.9.01.1.sql does not match the filter+
+[Apr 16 10:21:48] INFO (SchemaUpgrader.java:89) - Processing upgrade file upgrade-oats.9.10.1.sql+
+[Apr 16 10:21:48] INFO (SqlScriptRunner.java:51) - Running script file C:\OracleATS\data\scripts\en\upgrade-oats.9.10.1.sql+
+[Apr 16 10:22:05] INFO (SchemaUpgrader.java:96) - Upgrade complete for schema Oats from version 9.01.1 to 9.10.1+
+[Apr 16 10:22:05] INFO (SchemaUpgrader.java:43) - Starting upgrade for schema Olt+
+[Apr 16 10:22:05] INFO (SchemaUpgrader.java:50) - Schema Olt is version 9.01.1+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script db_users.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script init_ats_dbs.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script oats.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script oats_template_data.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script olt.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script olt_sample_data.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script olt_template_data.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script otm.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script otm_sample_data.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script otm_template_data.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4b_to_v4c Oracle.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4b_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4d Access.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4d SqlSrv.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4e Access.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4e Oracle.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4e SqlSrv.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4f Access.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4c_to_v4f SqlSrv.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4e Access.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4e Oracle.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4e SqlSrv.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4f Access.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4d_to_v4f SqlSrv.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4e_to_v4f Access.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4e_to_v4f Oracle.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script Update v4e_to_v4f SqlSrv.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script upgrade-oats.9.01.1.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script upgrade-oats.9.10.1.sql does not match the filter+
+[Apr 16 10:22:05] DEBUG (SchemaUpgrader.java:82) - Script upgrade-olt.9.01.1.sql does not match the filter+
+[Apr 16 10:22:05] INFO (SchemaUpgrader.java:101) - Nothing to do for schema Olt. Schema version stays 9.01.1+

Trying to open youtube, QuickTime cannot open video.3gp, only a problem since upgrading to Mavericks

trying to open youtube, QuickTime cannot open video.3gp, only a problem since upgrading to Mavericks, what do I need to do please ?

You're right. It wasn't QuickTime itself. I solved all the problems myself.
The main reason why QuickTime files weren't working was because the newest audio driver from Creative released July 2007 (using their autoupdate) is apparently for Windows Vista (it has the name Vista in the update title). Why that update showed up on my Windows XP Pro system, I have no idea. So, I went to Creative's site and got the driver before the latest release, and all works well.
The Microsoft update (from June 2007, I noticed today, not July) is another issue. It's based around the file P17RunE.dll, which is something from Microsoft for the SoundBlaster. Not sure what it does, but I don't need it.
Sorry for wasting all your time on a non QuickTime issue, but thanks for the help.

Itunes problem Since upgrading to window10

ITunes problem Since upgrading to window10, my ITunes cannot see the My Cloud drive, also I keep getting an error when my WC control panel tries to scan the content.This drive has worked fine for almost a year and since upgrading to windows 10 my smart TV's and my other devises can't find the drive I have updated the firmware, done a factory reset. but still have massive problems.Anybody any Ideas

This is what I did, In windows credentials from the settings menu I added a windows credential using the IP address, and then the name of the pc with log in details. But during my messing about I also mounted the drive and deleted my C:drive Itunes folder. then re scanned my music once I could set the parameters to the right folder.Its working but I have to admit I am not sure which one solved the problem. WD still working on a reply.Hope you get it sorted.

Capture not working (since upgrade to leopard)

hi
i have upgraded my OS to leopard and since doing that if i try to open FCE with my camera attached (to the back of the mac via firewire) the rainbow wheel comes up and FCE just wont open until i turn the camera off. i also get the same problem if i try to capture anything, but without the camera on everything else works fine i can edit existing clips etc.
this was never a problem before i upgraded to leopard, are there some setting i need to change in order to get round this?
the reason i upgraded was to be able to use the magic mouse fully.
equipment i am using is as follows:
camera: Canon XM2
computer: power mac G5
OS: 10.5.8
FCE: 3.5.1

okay, i have done as you suggested and uninstalled FCE and then re-installed from the upgrade which appeared to work first time i went to use capture, but then went back to use it again the next day and i had the same problem again!!
but after a few times of plugging and unplugging the firewire it finally regognised that the camera was there, one of the odd things i noticed was that when i plugged it in to the back of my g-raid hard drive it did recognise that the camera was there and i could control it from capture but it didn't show any images from the camera?
any ideas from anyone as to why it seems to be working intermittently?

Networking down since upgrade to Leopard, even with 10.5.1

Since upgrading to 10.5 (and 10.5.1) I cannot connect to my networked print (HP7680) or see other PCs that are on my network. I can still get on the internet fine. Sometimes I can see the other PC on my network in the finder window but they come and go, very weird. I Can never get the printer to work. I use a D-link router. I have talked endlessly to Apple support and they referred me to D-link. I don;t think this is a router issuse as the other computers using the same router are working fine and I can still get on the internet. This started immeadiately after upgrading to 10.5, I'm quite sure that is the source of the problem. Any ideas on this frustrating issue?

See topic "Unable to browse Windows shares using Leopard?". Lots of information.

Vista license problems since updating to Leopard

I installed Windows Vista through Boot Camp Beta several months ago when I was on Tiger, and registration/activation went fine, and I've never had any problems with it. However, a few weeks after upgrading to Leopard and installing the new drivers, I started receiving warnings in my Windows session that I "may be a victim of software counterfeit", which I mostly ignored, but now it seems thirty days has passed since "my activation period expired" and it's denying me access to Windows without activation. Automatic online activation reads my copy of Windows as invalid, and when I enter the Product Key manually, it tells me the Product Key is already in use.
It's telling me I have to enter another product key if I have one, or buy a new product key/license. I paid full price for my copy of Vista from a valid software retailer - how is it that my computer/Windows no longer recognizes that the product key is in use because it was used by me, and how can I reset it so it works? I tried reinstalling Windows, and all I got was the same message about the product key with another 30 days to resolve the problem.

You can activate it via telephone to MS.
You give them some info that your system generates and they give you a key. It's that simple.
It happened to me once and the whole process takes a few minutes.

Problems since upgrading to Leopard

Similar Messages

Maybe you are looking for