A service pack fails to apply to Microsoft SQL Server with error 0×7358, 0×80070534 or “No account mapping”

-
The fix is as follows
http://www.incandetech.com/derek/2009/10/23/a-service-pack-fails-to-apply-to-microsoft-sql-server-2005-with-error-0x7358-0x80070534-or-no-account-mapping/

But it does not apply to 32bit ms sql server installed on 64bit system. The registry path HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.x\Setup should be HKLM\Software\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.x\Setup

Ref: http://support.microsoft.com/?kbid=925976

Comments

Post a Comment

Popular posts from this blog

Save Settings for TeamViewer Portable

-
Work with TeamViewer.ini situated in \TeamViewerPortable\App\teamviewer folder. Setting nosave=0 will save your settings, but in the registry, and that doesn`t make it portable. The thing to do is importsettings=1 wich activate the automatic settings import. TeamViewer Portable will import the settings from a file called tv.ini which has to be situated in the same directory as your TeamViewer.exe. You can create the tv.ini by exporting your settings in the advanced options of the full TeamViewer version (Extras > Options > Advanced > Show advanced options > Export settings for TeamViewer Portable). This works in the oficial portable release from TeamViewer.com. In the PortableApps.com release, tv.ini must be situated in \TeamViewerPortable\App\teamviewer folder. Also, by setting LogOutgoingConnections=1 in the TeamViewer.ini file you can force TeamViewer to write a log file with detailed information about your connections. This log file is used by the TV Manager...
Read more

cos(π/9)*cos(2π/9)*cos(3π/9)*cos(4π/9)

-
=sin(π/9)*cos(π/9)*cos(2π/9)*cos(3π/9)*cos(4π/9)/sin(π/9) =sin(2π/9)cos(2π/9)*cos(3π/9)*cos(4π/9)/[2*sin(π/9)] =sin(4π/9)*cos(3π/9)*cos(4π/9)/[4*sin(π/9)] =sin(8π/9)*cos(3π/9)/[8*sin(π/9)] =sin(π/9)*cos(3π/9)/[8*sin(π/9)] =cos(3π/9)/8 =1/16 In LaTex with MathML :   \(\displaystyle= { \sin\frac{\pi}{9}\times\cos\frac{\pi}{9}\times\cos\frac{2\pi}{9}\times\cos\frac{3\pi}{9}\times\cos\frac{4\pi}{9}\over\sin\frac{\pi}{9} } \) \(\displaystyle= { \sin\frac{2\pi}{9}\times\cos\frac{2\pi}{9}\times\cos\frac{3\pi}{9}\times\cos\frac{4\pi}{9}\over 2\times\sin\frac{\pi}{9} } \) \( ( \because \sin(x)\cos(y)=\frac{1}{2}\left[\sin(x+y)+\sin(x-y)\right] )\) \(\displaystyle= { \sin\frac{4\pi}{9}\times\cos\frac{3\pi}{9}\times\cos\frac{4\pi}{9}\over 4\times\sin\frac{\pi}{9} } \) \( ( \because \sin(x)\cos(y)=\frac{1}{2}\left[\sin(x+y)+\sin(x-y)\right] )\) \(\displaystyle= { \sin\frac{8\pi}{9}\times\cos\frac{3\pi}{9}\over 8\times\sin\frac{\pi}{9} } \) \( ( \because \sin(x)\cos(y)=\fra...
Read more

Windows 7 / Windows Search 4 does NOT support UNC network location indexing

-
WDS v3 gets the support, but Microsoft has disabled the support of UNC indexing in WDS v4, even the Windows Search in Windows 7. There're a lot of discussion about how to overcome this step-down functionality ( http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/afb904c1-1c61-4aae-b6b1-5cf525b9f8de/ ). There is a simple way. Go to  http://www.microsoft.com/download/en/details.aspx?DisplayLang=en&id=3383  to download a patch called UNCFATPHInstaller.msi . Although the KB states that the patch works only for Windows Server 2003, Windows Vista and Windows XP, it actually does work for Windows 7. After patching, the WDS v4 will recognize OTFS protocol handler, as seen in HKEY_CLASSES_ROOT. You could now specify indexing location in Group Policy, which format stated in ( http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx ) Please noted that the patch only supports 32 bit. Ref:  http://robsprotips.blogspot.com/2010/06/search-ne...
Read more