Screwed up and deleted playlists for updating

I cannot update my mini. I had too many songs and I guess it created a playlist of randomly selected songs. I thought by unchecking songs off my library I could select my songs I wanted. I deleted my previous playlists. Now my mini wont update. It says the playlists selected for updating no longer exist. How do I fix it so I can update again? Thanks

Cool. Thank you so much. That link did help and I saved it in case I screw up again or one of my friends screw up. LOL!
Actually I didn't need it. But I needed your advice to try it out.
What solved my problem was to install a new set of songs off my laptop. When I did that, it gave me a message saying do I want to relace all songs with ones on this computer or something like that. I said yes and got songs from my laptop on the iPod. Then this morning after getting your advice and link I went to the desk top. When I loaded the mini on to the Desk top it asked if I wanted to dump all the songs on the iPod and replace them with ones on this computer? I said yes and it said there were too many songs and would I like it to select a ramdon group of songs and it created a new folder labeled "flpaa's iPod selections". So it's working fine now. Thanks so much for your help. Take one gold star for your help.

Similar Messages

Tired and deleted playlist for iphone

Hello! First, let me apologize for asking a stupid question with a simple answer, I am sure haha. I accidentally deleted my "Purchased on iPhone" playlist from iTunes and I can not figure out how to recreate it. I have re-synced my phone, and looked to see if I could recreate it as a smart playlist, but I can not, and I finally tried recreating my library, no luck. Any suggestions on how to get it back?
Thanks!

the first line of my question should read : Using iTunes on my Mac I can deselect a track in a playlist so it doesn't play on that occasion without removing it from the playlist.

Will someone tell me what happen to my play list and how I can restore or get it back! Apparently, apple for the second time to screw up and delete all my music again!!!

Will some explain why apple for the second time manage to screw up and delete "all my play lists and music again"! How can I restore it or get my music back... If I can't get my music back the way it was the last time I used itunes I will sale both my ipod touches!!!

Just what were you doing when it happened?
Just sync it from your iTunes library.
You can redownload iTunes purchases by:
Downloading past purchases from the App Store, iBookstore, and iTunes Store

"All of the playlists for updating no longer exist"???!!

I created a few new playlists and deleted an old one in iTunes, and then when I plugged in my mini to update I get the message:
Songs on the iPod Kellee's iPod cannot be updated because all of the playlists for updating no longer exist"
There are no songs in my mini after this msg. I reset it, tried to update again, but got the same msg. Please help!!

Hi Kellee!
Why do people delete playlists?? Seems like you have the same problem someone I tried to help has. She got the exact same error message when she deleted a playlist. If I were you I would have shifted some songs around, changed the name of the playlist to something else but NOT deleted the playlist. I don't think you can get the same playlist back once you delete it. Question is why is your iPod not recognizing your new playlists and it's requesting to update the playlist you already deleted?? I'm afraid I can't help you but maybe someone else can. I just wanted to say this.

Playlists for updating no longer exist

i am a novice...i deleted my ipod nano playlist from source list...i also updated yesterday...no i keep getting a screen when i connect my ipod to computer that reads, "songs on the ipod cannot be updated because all of the playlists for updating no longer exist. but all songs remain in library....Help!

You will find this user tip useful for resolving the missing playlist issue: Hudgie - iPod cannot sync because one or more playlists are missing

"songs..can't be updated b/c all the playlists for updating no longer exist

My Ipod was "off power" for so long that it "forgot" all its music. Now when I plug it in to my base computer, rather then synching it says "songs on the ipod "name" cannot be updated because all the playlists for updating no longer exist"

Hey.
See if this can help;
http://discussions.apple.com/thread.jspa?threadID=121728&tstart=150
Cheers!
-Bryan

Re: Transactions and Locking Rows for Update

Dale,
Sounds like you either need an "optimistic locking" scheme, usually
implemented with timestamps at the database level, or a concurrency manager.
A concurrency manager registers objects that may be of interest to multiple
users in a central location. It takes care of notifying interested parties
(i.e., clients,) of changes made to those objects, using a "notifier" pattern.
The optimistic locking scheme is relatively easy to implement at the
database level, but introduces several problems. One problem is that the
first person to save their changes "wins" - every one else has to discard
their changes. Also, you now have business policy effectively embedded in
the database.
The concurrency manager is much more flexible, and keeps the policy where
it probably belongs. However, it is more complex, and there are some
implications to performance when you get to the multiple-thousand-user
range because of its event-based nature.
Another pattern of lock management that has been implemented is a
"key-based" lock manager that does not use events, and may be more
effective at managing this type of concurrency for large numbers of users.
There are too many details to go into here, but I may be able to give you
more ideas in a separate note, if you want.
Don
At 04:48 PM 6/5/97 PDT, Dale "V." Georg wrote:
I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save'button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for any ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
>
>
>
>
====================================
Don Nelson
Senior Consultant
Forte Software, Inc.
Denver, CO
Corporate voice mail: 510-986-3810
aka: [email protected]
====================================
"I think nighttime is dark so you can imagine your fears with less
distraction." - Calvin

We have taken an optimistic data locking approach. Retrieved values are
stored as initial values; changes are stored seperately. During update, key
value(s) or the entire retieved set is used in a where criteria to validate
that the data set is still in the initial state. This allows good decoupling
of the data access layer. However, optimistic locking allows multiple users
to access the same data set at the same time, but then only one can save
changes, the rest would get an error message that the data had changed. We
haven't had any need to use a pessimistic lock.
Pessimistic locking usually involves some form of open session or DBMS level
lock, which we haven't implemented for performance reasons. If we do find the
need for a pessimistic lock, we will probably use cached data sets that are
checked first, and returned as read-only if already in the cache.
-DFR
Dale V. Georg <[email protected]> on 06/05/97 03:25:02 PM
To: Forte User Group <[email protected]> @ INTERNET
cc: Richards* Debbie <[email protected]> @ INTERNET, Gardner*
Steve <[email protected]> @ INTERNET
Subject: Transactions and Locking Rows for Update
I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save' button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for
any
ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
------ Message Header Follows ------
Received: from pebble.Sagesoln.com by notes.bsginc.com
(PostalUnion/SMTP(tm) v2.1.9c for Windows NT(tm))
id AA-1997Jun05.162418.1771.334203; Thu, 05 Jun 1997 16:24:19 -0500
Received: (from sync@localhost) by pebble.Sagesoln.com (8.6.10/8.6.9) id
NAA11825 for forte-users-outgoing; Thu, 5 Jun 1997 13:47:58 -0700
Received: (from uucp@localhost) by pebble.Sagesoln.com (8.6.10/8.6.9) id
NAA11819 for <[email protected]>; Thu, 5 Jun 1997 13:47:56 -0700
Received: from unknown(207.159.84.4) by pebble.sagesoln.com via smap (V1.3)
id sma011817; Thu Jun 5 13:47:43 1997
Received: from tes0001.macktrucks.com by relay.macktrucks.com
via smtpd (for pebble.sagesoln.com [206.80.24.108]) with SMTP; 5 Jun
1997 19:35:31 UT
Received: from dale by tes0001.macktrucks.com (SMI-8.6/SMI-SVR4)
id QAA04637; Thu, 5 Jun 1997 16:45:51 -0400
Message-ID: <[email protected]>
Priority: Normal
To: Forte User Group <[email protected]>
Cc: "Richards," Debbie <[email protected]>,
"Gardner," Steve <[email protected]>
MIME-Version: 1.0
From: Dale "V." Georg <[email protected]>
Subject: Transactions and Locking Rows for Update
Date: Thu, 05 Jun 97 16:48:37 PDT
Content-Type: text/plain; charset=US-ASCII; X-MAPIextension=".TXT"
Content-Transfer-Encoding: quoted-printable
Sender: [email protected]
Precedence: bulk
Reply-To: Dale "V." Georg <[email protected]>

TS1492 When I go to iTunes and then check for updates. I can not do this action due to the fact iTunes will not connect to the internet although the internet is working just fine, what do I do to fix this issue? Apparently I am currently using iTunes 7.0.

When I go to iTunes and then check for updates. I can not do this action due to the fact iTunes will not connect to the internet although the internet is working just fine, what do I do to fix this issue? Apparently I am currently using iTunes 7.0.

If you're really using iTunes 7.0 you are very far behind the current version - maybe it is trying to connect to a decomissioned server. In fact I am kind of surprised it will run on a Macbook Air. Are you sure you are running iTunes 7?

Automatic blocking and deletion flag for temporary unblocked vendors/custom

Hi All,
Can you please help me IS there any Standard Reports for the Follwing,
*"automatic blocking and deletion flag for temporary unblocked vendors/customers in Master Finance SAP machines"*.
Please reply me as soon as possibly.
Thanks & Regards,
Pavithranad.
Moderator message: please research before asking, do not assign higher urgency than normal.
Edited by: Thomas Zloch on Mar 3, 2011 2:43 PM

In XK06, flagging Vendor for deletion, I get warning "vendor xxxxx has open items in company code xxxx". Does this mean open Invoice Items, pending payment in FI? Since this is just warning I can hit enter and go ahead and save.
- YES YOU ARE RIGHT. IT CAN ALSO INCLUDE OPEN PO.
But, I can come back to XK06 and UNflag this same vendor for deletion? How would it affect the open items/POs...etc?
- THAT'S WHY THE MESSAGE IS AN WARNING AND NOT AN ERROR. (My Opinion)
Does basis has to do some sort of execution in order to actually delete the vendor master from the database? Would basis get a error when there are pending open items for vendors flagged for deletion?
- NOT RECOMMENDED. ANY DATA CAN BE DELETED THOUGH. IF YOU ARE ON ECC 5.0 OR ABOVE AND USING SE16N TO DELETE, YOU WILL NOT GET AN ERROR.
What's the advantage of using XK05 (blocking/unblocking) over XK06 (flagging/unflagging for deletion)?
- NOT SURE IF THERE IS ANY ADVANTAGE.

I cant update my iphone and i tried going on my pc on itunes and clicking check for update button but it says that "itunes could not contact the iphone software update server because you are not connected to the internet".plz help

i cant update my iphone and i tried going on my pc on itunes and clicking check for update button but it says that "itunes could not contact the iphone software update server because you are not connected to the internet". But i checked my internet on both my pc and iphone and tried again but it still says the same thing. plzz plzz help

Were you definitely connected to the internet at the time? If you don't have iOS 5 on your iPhone then the only way to update it would be via iTunes, once updated to the latest version of iOS you'll be able to update your iPhone without connecting to iTunes "over-the-air".
Before updating however it goes without saying to Backup your iPhone, this should happen by default upon connecting your iPhone to iTunes.
Regards,
Steve

"playlist for updating no longer exists!"

Recently my ipod reached its full capacity so I could not add anymore songs onto my ipod, instead it created a seperate playlist of songs which were most played etc. However I accidently deleted that playlist and now my ipod is blank and won't let me put songs on it
the message reads : "songs on the ipod cannot be updated because all of the playlists selected for updating no longer exist"
does anyone know how i could fix this problem?
any help would be much appreciated
thanks!

Open iTunes prefs-> iPod and set it to Automatically update selected playlists and select a new playlist.

After 3.6.10 all add-ons disappeared and a search for updates showed none needed. How do I get them back?

I am running on a Mac OSX 10.6.4. After updating Firefox to 3.6.10, a few add-on disappeared. Specifically, Delicious, 1Password, Stumble ON and Buckts. I looked for updates and none were available. I've run through the view menu and preferences but can't find an option to restore these functions. Do all these add-ons need to be updated to be compatible with 3.6.10 or is there something in the update that wiped out these views.

Add-ons that worked in 3.6.9 and earlier versions of 3.6 should also work in 3.6.10.
The first thing I would try is to delete the files that store details of installed add-ons. If one of those files is corrupt it can cause problems with add-ons not being listed. For details of how to do that see the corrupt extension files section of the [[Unable to install add-ons#Corrupt extension files|unable to install add-ons]] article.

Use of Creatable ,Updateable and deletable checkbox for entityset in ODATA

Hi Experts,
i have created one entityset without specifying creatable,updateable and deletable checkbox, and i am able to perform create,update and delet entity operation. Then what is the use of those checkbox.
Regards
Saumya

Hi,
Refer this document SAP Annotations for OData Version 2.0 and Creating Data Objects - SAP NetWeaver Gateway - SAP Library and Entity Sets - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library
Check for the default value mentioned in SAP Annotations for OData Version 2.0 for creatble, updateble etc attributes.
Regards,
Chandra

Transactions and Locking Rows for Update

I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save' button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for any ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
[email protected]------------------

I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save' button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for any ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
[email protected]------------------

For those who run Windows 8 with bootcamp: Do you update windows 8, with windows update? I have the latest bootcamp drivers, and never checked for updates on windows. Do you normally update windows 8?

Windows 8 has been running very well after installing it with bootcamp and its latest drivers.
I just have never updated Windows 8 itself, (windows has never checked for updates), and just has been
using it bare. Do you update windows 8 to the latest updates with windows 8, and have any problems
with the updates? Just curious before I start updating it for once.

You have to update Windows to the latest version with Windows Update and keep it updated, because this is a matter of security. Microsoft provides a lot of security updates and you have to install them even if you have got an antivirus. Then you can find other updates, and if you want to install Windows 8.1, just install all updates with Windows Update, and then go to the Windows Store and download Windows 8.1.
Apple says that Windows 8.1 is not supported by Boot Camp, but people say it works without any problem with the most recent drivers, so I do not find any risk after upgrading to Windows 8.1.

Screwed up and deleted playlists for updating

Similar Messages

Maybe you are looking for