August 2008 - Version 1.1.4:
Download Now!

I've seen a *lot* of hits on my post "Visual Studio 2008 Is Pretty Damn Slow…", which means that a lot of you are probably still experiencing speed issues with Visual Studio 2008. In regard to this, I thought it might be prudent to post information about the recently released Service Pack 1 for VS2008 and where to find it:

Visual Studio 2008 Service Pack 1 (SP1) and .NET Framework 3.5 SP1 Downloads

Visual Studio 2008 SP1 and .NET Framework 3.5 SP1 significantly improve the developer experience during the development process, and at runtime. These improvements address top issues reported by customers. For more information, see Visual Studio 2008 SP1 and .NET Framework 3.5 SP1.

Downloads

• Visual Studio 2008 SP1
• .NET Framework 3.5 SP1
• Visual Studio 2008 Express Editions with SP1
• Visual Studio Team System 2008 Team Foundation Server SP1

Additionally, the original hotfix which was intended to fix the speed issue (and is probably integrated into VS2008SP1) is available here:

• Downloadable Hotfix: Performance and Editor fixes for Microsoft Visual Studio 2008 and Visual Web Developer Express 2008

And...

Here are all my posts related to this Visual Studio 2008:

• Visual Studio 2008 Is Pretty Damn Slow…
• …but its programmers are on the ball.
• Performance and Editor fixes for VS2008…
• Visual Studio 2008 Hotfix Is Excellent!
• Multi-Targeting VS2005 and VS2008 Web Application Projects, a Gotcha!
• Linkback: "Visual Studio 2008 C# IDE is Slow … Really slow."
• Getting started with VisualSVN « Mike In Madison
• Google: Top Billing

Users were reporting that the PPTP VPN was no longer available. Checking the logs I found nothing out of place (Routing and RAS was started and the snap-in didn't report any issues). I rolled back the Windows Updates and the PPTP became active.

I've just attempted to install the v2 update to the KB article and the same problems occur. Do not install this update!

There is an "official" MS blog post however there is nothing noting the PPTP issues that occurred for me. I actually posted a comment with my particular situation on the comments page - however they haven't approved the comment. http://blogs.technet.com/sbs/archive/2008/07/09/hold-off-on-installing-hotfix-948110-on-sbs-2003-servers.aspx

Microsoft's KB article didn't uncover any reasons why my PPTP connectinos failed - http://support.microsoft.com/kb/948110

First there was a service pack released for SQL Server 6.5 that would start rebooting my system at random. The bad news was that there was no back out plan and we had to rebuild that box from the ground up. Looking back on this we should have tested it first, a hard way to learn.

Second I think most of us can remember SQL Slammer. I did not apply a service pack fast enough and my team and were up all night patching servers, and rebooting them.

There are also considerations for your hardware that you have to consider. I use to be on a SAN that I will not name. Our SAN was having some performance issues time and time again. It felt like we were up night after night working on this thing. But each time we talked to the vendor it appeared like they wanted nothing to do with us until we were up to the latest version. They would release a new version almost every week and that really put us in a bind that the piece of equipment that was supposed to keep us up and running all the time was making us reboot it more often then we had ever rebooted our pre-SAN machines.

The end results in my opinion are the same. Here is what I look at when I make a decision to apply a service pack, hot fix or a firmware upgrade:

• Look at the release notes is there major security problems that this patch will fix. If so start the process ASAP.  The fact that the patch is out there means that someone else has found it and is using that vulnerability and if that is not the case they know now.
• If it’s not a security fix and you are not waiting on a functionality fix then I will wait for a month or two to see if there are any bugs and if so how they get worked out.
• Wait 24 hours and look on the internet for problems for the patch, make sure that if issues are out there that you are not going to face those issues.

I recommend that you draw your own opinion. As I mentioned in my examples, I have been bit by doing it to soon and not doing it soon enough.

Microsoft have just released a hotfix to search DCOM permission post SP1 problem which I wrote about previously.

The hotfix can be found here. http://support.microsoft.com/kb/953137

Hotfix PSE450R02W2K3007 - For Citrix Presentation Server 4.5 for Windows Server 2003

http://support.citrix.com/article/CTX116967

My new PC showed up on Friday late in the afternoon. I quickly unpacked it and put it upstairs in my office. I plugged it into my KVM switch and connected it to my router to get to the Internet... and then proceeded to spend the next several hours downloading all the patches and upgrades I needed.  Before I could even start, I had to download patches to the patch downloader. My old computer downloads patches every couple of days and installs them in the middle of the night. I hadn't really thought about how many patches we were talking about until I had to do them all at once.

Actually I would have preferred doing it all at once. Instead, I downloaded the patch downloader and it reported I should get Service Pack 2. Fine. I love a patch that is bigger than the application it's updating. That took about an hour on my cable modem (I have no idea what people on dial up do; I suppose they run Windows 95 still and it doesn't matter). After the install and obligatory reboot, I found I had to download pages of patches for Service Pack 2. I counted 66 separate updates before deciding to go to Service Pack 3. Even that had a few security hotfixes.  Once I was done with Windows, then I had all the ancillary programs to deal with. I upgraded to Internet Explorer 7 (though I have to say I still like Firefox better). I probably downloaded half a dozen updates to Windows Media Player. The sun was down and dinner was done before I finally got to my machine specific ones. I needed an updated video driver. My network connection needed a fix though it had no problem downloading a gigabyte worth of patches beforehand.

I put Daniel to bed and retired to my office to do the final reboot. I checked Windows Update one last time and - lo and behold - there was nothing left on the list! I had a fully up to date computer... until I looked over at the Office CD sitting on top of the pile of software I want to install.

I decided to hold off on that for now.

Всички предишни trial кодове, са подновени за да може всички юзъри (независимо от това коя версия ползват) да могат да си пуснат теста, след ъпдейтване на версията.
Ако вече сте използвали трайл код, можете да си ре-рикуестнете такъв, като въведете същият имейл, в трайл код рикуест страницата: service.futuremark.com/3dmvantage-trial.action

Hotfix-а може да бъде свален от официалният сайт и мирърите изписани тук: www.futuremark.com/download/3dmva_hotfix_101/

Пълна инсталационна версия на 3DMark Vantage, заедно с хотфикса е налична тук: www.futuremark.com/download/3dmarkvantage/.

Happy benchmarking!

3DMARK VANTAGE HOTFIX NOTES 1.0.1
Overview:
We have made changes in the product editions to better serve our customers. Off- line score is now available in the Advanced edition, and ad banners have been removed. Error messages have been improved, and various bugs have been fixed.

IMPORTANT: The scores are NOT affected by this hotfix, and will remain compatible with version 1.0.0 scores.

Installation:
If you have previously installed the 1.0.0 version of 3DMark Vantage, you can use the smaller 3DMark Vantage Hotfix installer to update to version 1.0.1. Just follow the installation instructions on screen.

If you have not previously installed 3DMark Vantage, you need the full installer package. Run the installer, and follow the instructions on screen.

IMPORTANT: We recommend that you only install 3DMark Vantage using a user account that has Administrator rights on the machine. Installing 3DMark Vantage as a Standard User on Vista is not recommended. Cases where the user has Standard User rights only, and User Account Control
(UAC) turned off are specifically not supported, and will not work.

If you have previously installed 3DMark Vantage with Standard User rights, and have any trouble installing the hotfix, please un-install 3DMark Vantage, and re-install using the full installer, using a user
account that has Administrator rights on the system.

After the installation, 3DMark Vantage may ask you again for your serial key. Please enter it as previously.

Futuremark encourages everyone to download the latest build (1.0.1) to ensure best compatibility and functionality.

Changes:
1. Off-line score viewing is now available in the Advanced Edition.

2. Score save / submit saved options are now available in the Advanced Edition.

3. Ad banners have been removed from all editions.

4. Added a "SEND ERROR" button to error messages; clicking this will send detailed error information to Futuremark for better bug tracking and fixing. No personally identifiable information will be sent or stored.

Fixes:
1. An issue preventing valid serial key entry in some cases has been fixed.

2. An issue causing "boost::filesystem::create_directory" error message after registration has been fixed.

3. Added a check and error message for hardware that is not DX10 capable.

4. Improved detection of supported resolutions so that CPU test minimum requirement (1280x1024) is now taken into account correctly.

5. Fixed an issue where pressin the ESC key during CPU test loading screen, the user would be taken to a score view with score -1.

6. The entire 3DMark Vantage application is now elevated to Administrator rights, rather than only the SystemInfo component. This will ensure more robust SystemInfo and benchmark functionality, and
fixes the "pop-behind" elevation dialog.

7. Fixed an issue that sometimes caused "WM_QUIT" error messages.

8. Post-processing scale is now displayed correctly in the UI for the Extreme Preset.

9. Fixed an issue that could cause resolution switches at test runtime.

El pasado 28 de abril, Futuremark lanzo su nuevo benchmark para tarjetas graficas 3DMark Vantage, exclusivo para Windows Vista y tarjetas DirectX 10, sin embargo, a poco de su salida se encontraron algunos problemas con los drivers tanto de ATI y NVIDIA.

Ambas empresas lanzaron sus respectivos Fix (arreglos) y ahora lo ha hecho Futuremark quien ha lanzado finalmente el anunciado HotFix (arreglo importante) para 3DMark Vantage, cuyos cambios y mejoras puedes revisar en las Notas de Lanzamiento, el parche pesa 15.5MB si ya tienes 3DMark Vantage o si deseas bajarlo con el parche incluido debes descargar los 450MB.

 
Was ist ein "Update Rollup"?

Ein "Update Rollup" Paket ist ein Software-Paket, in dem sich eine Sammlung von wichtigen Softwareaktualisierungen (Hotfixes) befindet, welche die Funktion und/oder die Stabilität einer Software verbessert.
Für Exchange gibt es seit der Version 5.5 in regelmäßigen Abständen Update Rollups. Ein Update Rollup Paket mit einer höheren Versionsnummer beinhaltet alle Hotfixe der Vorgängerversion. Um auf dem aktuellsten Stand hinsichtlich Funktion und Stabilität zu sein, muss also immer die letzte Version des ServicePacks und die letzte Version des Update Rollups installiert werden. Ältere Rollup Pakete müssen nicht deinstalliert werden
ABER: Wenn zwischenzeitlich ein spezieller Hotfix für Exchange 2007 (ein sogenanntes Interims Update) instelliert wurde, dann muss das vor der Installation des Updates Rollup 6 deinstalliert werden.
 
Ein "Update Rollup" beinhaltet in der Regel keine "Security Hotfixe". Diese müssen separat über Microsoft-/Windows Update installiert werden!

 
Faustregeln zur Implementierung

Gerade in kritischen Umgebungen, wo Hochverfügbarkeit eine Rolle spielt, ist es genau wie bei der Implementierung von ServicePacks immer ratsam eine Weile Zeit ins Land gehen zu lassen, bis man das Paket installiert. Grund dafür ist, dass sich Fehler in das "Update Rollup" eingeschlichen haben könnten, die erst nach Veröffentlichung bekannt werden.

• Installation in einer nicht produktiven Testumgebung
• Durchführung aktiver Tests (Standardfunktionen, Outlook-basierende Applikationen)
• 2 bis 4 Wochen auf eventuelle Microsoft Meldungen hinsichtlich Problemen warten und Newsgroups lesen
• Installation in Produktion und dokumentieren des genauen Vorgehens (vor Beginn Datensicherung!)

Probleme die das Update Rollup 2 behebt

940462 The public folder store may take several minutes to mount on an Exchange 2007 server

944153 Exchange Server 2007 does not have Transport Neutral Encapsulation Format (TNEF) capabilities for POP and IMAP protocols

945917 You receive an error message when you try to access the Microsoft Office Outlook Web Access global address list in a Microsoft Exchange Server 2007 environment

947346 Exchange Server 2007 mailbox users cannot retrieve the free/busy information for Exchange Server 2003 mailbox users in a large Exchange Server organization that has more than 100 administrative groups

947360 Error message occurs, and users cannot access the free/busy information after you use the Import-Mailbox cmdlet to import data to a mailbox in Exchange Server 2007 Service Pack 1

947391 The contents of .pst files are not imported into Exchange Server 2007 mailboxes when you use the Import-Mailbox cmdlet

947451 A recipient sees unexpected text in the top of an e-mail message that you send in Exchange Server 2007

947458 The Edgetransport.exe process may crash on an Edge server that is running Exchange Server 2007 Service Pack 1

947551 The Edgetransport.exe process may crash intermittently on an Exchange Server 2007 Service Pack 1 Edge server

947577 If you try to connect a mobile device to a mailbox server through a server that is running Exchange Server 2007, the mobile device may be unable to connect

947646 Event ID 12011 is logged every time that the MSExchangeTransport service starts after you install Exchange Server 2007 Service Pack 1 on a computer that is running the German version of Windows Server 2003

948047 An event ID 1080 message is logged in the System log every three seconds after you run the Set-ExchangeServer command to set the static domain controllers on an Exchange 2007 cluster node

948297 The OOF template may be delivered as an attachment in an Exchange 2007 environment when you use the "Reply with Template" option in Microsoft Outlook

948332 Failover takes a long time to finish in an Exchange Server 2007 cluster continuous replication environment

948374 The EdgeTransport.exe process crashes intermittently, and event ID 1033 is logged in Exchange Server 2007

948666 When you try to migrate a mailbox from Exchange Server 2003 to Exchange Server 2007, the Exchange Management Shell may stop responding

948830 The MSExchangeSyncAppPool application pool crashes on a server that hosts an Exchange Server 2007 Client Access Server role

948831 A user may be unable to synchronize with an Exchange Server mailbox from a mobile device when a Client Access server has been upgraded to Exchange Server 2007 Service Pack 1

948844 An exception occurs, and event IDs 4999 and 5000 are logged when you modify the Outlook Web Access user interface

949186 When you try to run the Restore-mailbox cmdlet on a server that is running Exchange Server 2007, you receive an error message

949193 The address rewrite agent does not rewrite the address for Out of Office (OOF) messages in Exchange Server 2007

949463 An exception error is generated after you run a Set-AttachmentfilterListConfig command together with the ExceptionConnectors option on an Exchange 2007 S949463-based server

949541 You cannot log on to Outlook Web Access Light, and an error message occurs in Exchange Server 2007

949703 Error message in Outlook when you click the signature icon of a signed e-mail message that an Exchange Server 2007-based Edge server receives: "The digital signature is invalid"

949726 After you install Exchange Server 2007 Service Pack 1, the Set-ExcecutionPolicy task causes an error message, and event ID 103 is logged

949772 If you run the "isinteg -dump" command against a dismounted store on a server that is running Exchange Server 2007, the Store.exe process stops unexpectedly

950123 Error message after you apply Update Rollup 1 for Exchange Server 2007 Service Pack 1 in a Japanese environment: "Public Folder Management Console is not an allowed Snap-in"

Link zum Download

http://www.microsoft.com/downloads/details.aspx?displaylang=de&FamilyID=99da32e0-d9e3-4156-aabf-8369bf96e3e7

 
Weitere Informationen zum Update Rollup 2 bei Microsoft

http://support.microsoft.com/?kbid=948016 

 
Installation des Update Rollup 2

! Hinweis !

Wenn eine Exchange Cluster Installation vorliegt, dann muss vor der Installation folgendes sichergestellt werden:

• das Setup sollte zuerst auf dem passiven Knoten (Node B) durchgeführt werden
• auf dem aktiven Knoten müssen alle Exchange Cluster Ressourcen beendet werden und der Cluster Service muss angehalten und möglichst auf Startart "deaktiviert" gestellt werden
• nach erfolgreicher Installation muss der Cluster Service wieder reaktiviert werden
• die Installation auf dem aktiven Konoten kann nach einem Schwenk der Ressourcen erfolgen
• auch hier sollte der Cluster Service während der Installation gestoppt und deaktiviert werden

Gerade und besonders wenn Exchange Im Cluster betrieben wird, sollte vorab die Installation des Update Rollups in einer Testumgebung durchgeführt werden!

Ein Neustart des Exchange Servers wird nach der Installation des Update Rollups nicht immer gefordert. Ich empfehle diesen aber auf jeden Fall.

 
Links zum Thema
aktuell noch keine

 
Keywords: Exchange 2007 Update Rollup 1 Servicepack Hotfix KB945684

Resolution: 

The solution is as under: 

1- Install WSS Service Pack 3  

http://www.microsoft.com/downloads/details.aspx?FamilyId=2BBFC89B-EB59-49FF-B58F-684693CB25A7&displaylang=en 

2- Install SharePoinr SharePoint Portal Server 2003 Service Pack 3 (SP3)  

http://www.microsoft.com/downloads/details.aspx?FamilyId=2BBFC89B-EB59-49FF-B58F-684693CB25A7&displaylang=en 

Hopefully the problem will be solved.  

This may generate a new error when you try to view Documents / list items using "Eidt in DataSheet" option following error may occur: 

“The list is displayed in Standard view. It cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Windows SharePoint Services is not installed, your browser does not support ActiveX controls, or support for ActiveX controls is disabled.” 

you don't need to worry 

3- Install hotfix. From the following URL, send request to Microsoft. 

http://support.microsoft.com/kb/943167 

Edytujemy rejestr i szukamy takiego wpisu:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\tifm21\Parameters

i zmieniamy wartość SDParam z liczby 16 (dziesiętnie) na wartość 1 (dziesiętnie).

Innym łatwym sposobem jest pobranie poprawki o nazwie: The 923293 hotfix adds support for SD High Capacity memory cards in Windows XP.

After you have installed Service Pack 3 (SP3) on your SharePoint Portal Server 2003 and try to use the “Edit in Datasheet” feature, you may receive the following error message: 

“The list is displayed in Standard view. It cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Windows SharePoint Services is not installed, your browser does not support ActiveX controls, or support for ActiveX controls is disabled.” 

Google this on the internet and you will find most solution containing instructions about the Microsoft Office 2003 Professional Edition. Some may be work around like changes in the Registry. 

If this problem is on the server, it is desirable to visit the following link on Microsoft site and take appropriate actions based upon your own risk analysisL.  

http://support.microsoft.com/kb/943167

I worked with Microsoft and finally got a hotfix that resolves this issue.

The KB article can be found here: http://support.microsoft.com/kb/950282

I have been using a private build for a few weeks now and it definitely has solved the problem I was experiencing.

Mini Update
18 Mar 2008

It is no longer possible to place auction orders for limited items.

Originally Posted Here

Since this is pretty vague, i did some research in order to gather more information about this action.

I first started by searching on google for a possible explaination for the removal of this function and if a bug/exploit was the reason for removing it. After 2-3 hours of searching on google, i haven't find anything usefull.

So i decided to call MindArk and ask if there is more information about this case. As always, they wheren't pretty cooperative all got was that this feature was disabled for security reasons and may be re-enabled again in the future.

While that's not much information to start off, it told one thing: The reason for the removal of the order option for limited items seems to be connected to a bug or exploit and was removed until a permanent fix can be applied.

So i decided to checkout some of the popular cheat and exploit forum and comunities, to see if there is more information about this bug. Going through a few of the free accessible cheater comunities, i haven't found anything suspicious.

Since i don't have any payed subscriptions for the other forums and comunities which can only be accessed for subscribers, i decided to use some of my old contacts i've met in my online gaming career from who i know that they were active in this underground cheaters comunity.

It took them a few hours, until one contacted me and said that he maybe found the reason for the removal of this feature.

The real reason behind the removal is a bug with the orders. This bug happens with (L) items which have a very high TT value (TT > 1000 PED). If you use an insane markup percentage, the money necessary for the order will turn over negative. And if you increase the markup even more, the numbers will eventually become positive, but below TT value of that item.

You can see the prove on the picture below it. It is still in tact in the current client and can be tried too (you can play with it to see that this bug is for real, just don't press "Order" if you don't wanna risk your account. MindArk may monitor this and ban/log such attempts). My contact said that it was confirmed from several people in this subscribers only cheater forum, that it was possible to put order for Items with very high TT value for 1-2 PED in total (1 PED fee for the order + 0-1 PED for the itemitself).

With todays fix, the ability to put any limited (L) order into auction was disabled, effectivly stoping this exploit from working. As pointed out from Support this will probably be only a temoprary workaround until the real bug is fixed or the system is reworked.

But it's unknown how long this bug exists and how much damage may be already caused by it. But it's good to see that MindArk reacts and stop it from working, even if it negativly affects some people who often order (L) items. But this is a necessary sacrifice in order to prevent exploiters from abusing the system to gain unfair advantages.

Download: Service Pack 1 for Windows Vista 32 Bit [434.5 MB]
Download: Service Pack 1 for Windows Vista 64 Bit [726.5 MB]
View: Windows Vista SP1 Overview
View: Notable Changes in Windows Vista SP1
View: Hotfixes and Security Updates included in Windows Vista SP1

Finally today I thought I'd search for this error message to see if anybody knew what to do about it. Turns out the problem is solved by a hotfix which you can download from Ugh's Graymatter Honeypot. I tried it and it works like a champ now. My electric bill with thank him.