Upgrading 3.3 -> 3.6.1 results with new issue

[Vyacheslav]

We've updgraded ProGet from 3.3.5 to 3.6.1.
But after that we've received a permanent issue with package restoring.

Like that:

nuget restore C:<path to sln>.sln -NoCache -Source http://<correct path to proget feed> -Verbosity detailed

GET http://<correct path to proget feed>/Packages(Id='<PackageName>',Version='1.0.0.227')

System.InvalidOperationException: Unable to find version '1.0.0.227' of package 'PackageName'.
в NuGet.PackageHelper.ResolvePackage(IPackageRepository repository, String packageId, SemanticVersion version)
в NuGet.Commands.RestoreCommand.RestorePackage(IFileSystem packagesFolderFileSystem, String packageId, SemanticVersion version, Boolean packageRestoreConsent, ConcurrentQueue1 satellitePackages) в NuGet.Commands.RestoreCommand.<>c__DisplayClass5.<>c__DisplayClass7.<ExecuteInParallel>b__2() в System.Threading.Tasks.Task1.InnerInvoke()
в System.Threading.Tasks.Task.Execute()

Version 1.0.0.227 IS EXISTS ON THE FEED and it's LAST version of the package. So I guess there is some correlation with old issue: http://inedo.com/support/questions/2136
(maybe not... who knows...)

This issue completely shutted down our package processing and I have no ideas how to resolve this.
Reverting to 3.3.5 is a backup option for us if nothing helps in a few days .

Any ideas? Is there enough information to investigate?

Thanks!
Vyacheslav

Product: ProGet
Version: 3.6.1

[Vyacheslav]

We've reverted to 3.3.5. Looks like an 'Unable to find version' issue resolved...
But I don't know what to do next... Lives on 3.3.5 forever?..

[Alana]

You will need to use Fiddler to determine the EXACT urls that are causing a problem during package restore; we can then investigate what query is causing the problem.