"iTunes Library file cannot be saved". What is this all about?

Had the same issue running itunes 9 on windows 7 while importing cd's

Have a look at the end of this thread:
http://discussions.apple.com/thread.jspa?messageID=7463672

I did the same with indexing in windows, seems to work

Have a look at the end of this thread:
http://discussions.apple.com/thread.jspa?messageID=7463672

Method I used to exclude the itunes folder from windows indexing in win 7 (based on the itunes library folder being stored in the music folder):

Clicked start,
typed in the search box "Indexing",
went to indexing options,
from there went to modify,
in the *change selected locations* area I expanded the drive that windows was installed on,
expanded the users folder, then the username folder, then the music folder,
I then unchecked the itunes folder and selected ok.

After doing this I also deleted the temporary file as done in the end of the thread quoted above.

Since then the "iTunes Library file cannot be saved" message seems to have
disappeared.

Cheers, this seems to work. I had the same problem running iTunes 9 in Windows 7, problem solved.

Glad this helped

Hello all

It seems that there are two issues here.

One with Virus Checkers and one with Indexing.

In my case I keep my library and music files on a NAS which is not Indexed and my issue was fixed by excluding the iTunes directory on the NAS from my Virus Checkers Real Time Scanner.

Others, as has been evident in this thread fixed there issues by excluding the iTunes directory from being Indexed.

I wonder if we could get this thread Stickied so that others with similar problems in the future can find this thread easily.

Thoughts?

Bye for now

Kevin

Hi Kevin. You've been doing nice work on this issue.

With regard to the antivirus causes of this sort of thing ... although Nod32 seems to be the most commonly confirmed culprit, it might be worth keeping an eye out for folks with BitDefender, too.

Just saw this yesterday (droideka9's post):

http://discussions.apple.com/thread.jspa?messageID=10521384#10521384

Thinking it might possibly be relevant, since BitDefender here was producing similar sorts of store effects to what NOD32 can do. So if it was producing similar problems in one respect, it might be capable of causing similar library-file-save problems.

(I wonder if the indexing issue on Windows 7 might also ramify through to store problems too? A bit more difficult to tell with that, though ... there's a lot of different things that can go wrong with a store connection, and any Windows 7 indexing issues might tend to get lost a bit in the "noise" of the other issues.)

Hello b noir

Thanks.

I do not post very often but I will if I can help with an issue.

I will be upgrading (actually a Clean Install) from Windows XP Pro to Windows 7 Ultimate this week or next so I will see how I go with iTunes.

Bye for now

Kevin

I will be upgrading (actually a Clean Install) from Windows XP Pro to Windows 7 Ultimate this week or next so I will see how I go with iTunes.

Best of luck with that, Kevin!

Just a thought. It would probably be a good idea to deauthorise the computer (in iTunes) prior to doing the upgrade. Otherwise, the change in operating systems might well be enough to convince your Store content (after the upgrade, when you've shifted it back on board the PC) to believe that it's on a different computer than it was before, and you might end up with multiple authorisations on that PC.

Hello b noir

Thanks for that, something else I have to think about 🙂

Bye for now

Kevin

Running eset smart security which includes Nod32 with no settings changed

If this helps with anything

Message was edited by: Dae011

Running eset smart security which includes Nod32 with no settings changed

Crikey ... Dae, if you check through the following Eset document and apply workarounds relevant to the particular version of Nod32 you have with your Eset Smart Security, do you find that you're able to reenable your Windows Indexing (in the areas in which you've disabled it) without getting the troubles with iTunes any more?

http://kb.eset.com/esetkb/index?page=content&id=SOLN760&actp=search&viewlocale=e n_US&searchid=1256931434241

Crikey ... Dae, if you check through the following Eset document and apply workarounds relevant to the particular version of Nod32 you have with your Eset Smart Security, do you find that you're able to reenable your Windows Indexing (in the areas in which you've disabled it) without getting the troubles with iTunes any more?

Will give this a go, I will post back later with the results (Running version 4 of eset smart security).

Hello

I am also using version 4.0.467.0 of Eset VC.

As I said previously there seems to be two issues at work here.

Bye for now

Kevin

Well reenabing indexing on the itunes folder bought back the *"iTunes Library file cannot be saved"* message (also creating some temp files), but doing what was in the Eset document and seeing this resolved the issue for Kevin is likely to have worked with me.

Hello Dae011

As I mentioned earlier in this thread I have my music and iTunes library stored on a NAS which is not indexed.

Your most recent post is slightly confusing.

Do you mean that you have reenabled Indexing and applied the fixes outlined in the Eset document which has also fixed your issue?

If so then I wonder if there is a conflict between Indexing and the VC Real Time Scanner where one can be active at a time but not both.

Bye for now

Kevin