I always forget this until I need it the next time, but there is a great post that talks about how to fix your skype quality. http://pauloflaherty.com/2008/03/26/improve-skype-quality-with-these-tips/
1. In Skype, Go to Tools > Options > Connection. Select the option to use ports 80 and 443. In the “Incoming Connections” box you can chose any port between 1024 and 65535.
2. Reconfirm that your firewall is correctly configured. Follow the simple visual guide here:
3. Quit any file sharing applications or high-bandwidth usage applications.
4. For more detailed security setup on a network:http://www.skype.com/security/guide-for-network-admins.pdf (does not work anymore)
5. If these suggestions do not resolve improve call quality, follow these steps:
* Quit Skype
* Locate the shared.xml file found in
C:\Documents and settings\Your Windows Username\Application data\Skype\shared.xml
* Delete the file called shared.xml
* Restart Skype ( shared.xml will be recreated )
Note: Showing hidden folders and files has to be turned on: please navigate to :
In XP – My Computer > Tools (Menu) > Folder Options > View.
In Windows 7 – Open Explorer >Organize (Menu)> Folder And Search Options > View.
Once there, please make sure that the option “Show Hidden Files and Folders” is enabled.
6. Disable Quality of Service packet scheduling. Go to Start -> Control Panel -> Network Connections. Right click on the connection you are using. Select Properties. Untick the “QoS Packet Scheduler” option.
I do steps 1-3, 5, and 6. For step 2, please make sure your firewall is port forwarding your skype port to the proper computer. That is where you get the best performance.
Step 5 is a maintenance one that you will find yourself doing from time to time when things start to slow down. Instead of deleting shared.xml, I just append the date to the end of it in YYYMMDD format.
Hope this helps someone that is trying to improve conversations with Skype.
When working with EF Database First (don’t ask) and mapping stored procedures you may run into this issue.
Julie Lerman has written a great story on how to do the mappings and has some code to download to inspect how to set up the mappings for insert, update, and delete appropriately for use with stored procedures (http://msdn.microsoft.com/en-us/data/gg699321.aspx).
You may have searched everywhere else and have not been able to find a satisfactory answer. In some cases your model has a circular dependency and there are multiple search results that will help you with that out there.
In my case the problem came down to using a Manage type sproc that would handle both insert and update. As you can imagine you would pass in the primary key field to the Sproc no matter what.
Entity Framework believes this is an association (possibly to a foreign key) so it gives the error above. When you convert it to using separate Insert and Update stored procedures where the insert does not pass in the PK, everything works appropriately.
So if you are getting the above error, make sure you are not mapping the PK in the insert procedure.
Hope this helps some poor soul who falls upon this issue.