Error when trying to upgrade SMF 1.1.15 to 1.1.16
It has been reported by many SMF users that they are facing problem to upgrade SMF version from SMF 1.1.15 to 1.1.16 automatically. You may receive the following error while upgrading SMF 1.1.15 to SMF 1.1.16:
The package you are trying to download or install is either corrupt or not compatible with this version of SMF
You might not encounter this error in previous version.
Instead of upgrading it manually, there is a workaround to upgrade it automatically. You just need to follow the below steps:
[1] Download upgrade package from the following URL:
http://custom.simplemachines.org/mods/downloads/smf_patch_1.0.22_1.1.16.tar.gz
[2] Extract the archive using WinRAR or other software.
[3] Now zip the extracted folder to .zip extension let us say “smf_patch_1.0.22_1.1.16.zip”.
[4] Upload this zip file in your packages directory.
[5] Login to the administrator area and use the package manager to find and to install the “smf_patch_1.0.22_1.1.16″ file.
This should work who are facing problem to upgrade version automatically.
Kailash Aghera
Web Application Gallery module is unavailable
If you have upgraded your WebsitePanel version to WebsitePanel 1.2.0, you may receive the following error while accessing Microsoft Web Application Gallery:
Application Gallery module is unavailable:
- MsDeployIsNotInstalled.
You may receive even if MsDeploy 1 and MsDeploy 2 are installed on your server. The solutions are different for 32-bit and 64-bit operating systems.
[1] Fix for 64-bit operating system:
- Install the latest version of MS Deploy (x64 version):
http://www.iis.net/download/WebDeploy
- Run WebsitePanel Server application pool in 64 bit mode .
- Restart IIS service.
[2] Fix for 32-bit operating system:
You will need to make changes in Windows registry.
- Open registry to change MsDeploy v1 path.
- Go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\1]
- Under “InstallPath_x86” enter the value C:\Program Files\IIS\Microsoft Web Deploy\ (or path of ms deploy 1 installation)
- Go to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IIS Extensions\MSDeploy\2]
- Under “InstallPath_x86” enter the value C:\Program Files\IIS\Microsoft Web Deploy V2\ (or path of ms deploy 2 installation)
Do NOT forget to restart IIS after making above changes.
Kailash Aghera
How to optimize MySQL database using phpMyAdmin
Whenever you delete large number of records from your MySQL database, it is recommend to optimize your MySQL database for the best performance. In this article, we will show you how to optimize MySQL database using phpMyAdmin.
- Open your phpMyAdmin tool.
- Select the database you want to optimize on the upper left.
- Select the tables you want to optimize (usually checkmark all tables)
- Using the selection box at the bottom, select “Optimize Table”
This will execute the OPTIMIZE TABLE SQL query on the selected tables.
How to repair a corrupted MySQL database from cPanel and phpMyAdmin
Sometimes, your MySQL database may be corrupted and it requires to repair your MySQL database. Here we will provide you steps to repair corrupted MySQL database from cPanel and phpMyAdmin.
[1] Repair a MySQL database from cPanel
Log in to your cPanel and go to MySQL Databases. In the section Modify Databases, select a database from the drop-down box next to Repair DB: and then click the Repair DB button.
If the database engine used by your database supports repair (for example, MyISAM supports it), you will see a list of the repaired tables within the database.
If your database engine does not support repair (e.g. InnoDB database engine), you will get the following error message:
note : The storage engine for the table doesn’t support repair
[2] Repair a MySQL database from phpMyAdmin
- Open your phpMyAdmin and select the database whose tables you wish to repair.
- Select the tables you wish to repair, or simply click [Check All] to select all tables.
- Click the box [With selected:] and choose Repair table. This will execute the REPAIR TABLE SQL query on the selected tables and they will be repaired.
How to change the database storage engine of a MySQL database table
You may require changing MySQL database storage engine for your table.
Let’s assume that you have a database table called your_table using MyISAM engine and you wish to change the engine from MyISAM to InnoDB.
You can change the storage engine using the following MySQL query:
ALTER TABLE your_table ENGINE = InnoDB;
If you have phpMyAdmin, you can execute the above query from there.
Open your phpMyAdmin tool and select the database which contains your_table. Then click the SQL tab, paste the above query there and click the Go button.
WordPress 3.1 released
The long-awaited fourteenth release of WordPress is now available. WordPress 3.1 “Reinhardt” is named in honor of the jazz guitarist Django Reinhardt. Version 3.1 is available for download, or you can update from within your dashboard.
This release features a lightning fast redesigned linking workflow which makes it easy to link to your existing posts and pages, an admin bar so you’re never more than a click away from your most-used dashboard pages, a streamlined writing interface that hides many of the seldom-used panels by default to create a simpler and less intimidating writing experience for new bloggers (visit Screen Options in the top right to get old panels back), and a refreshed blue admin scheme available for selection under your personal options.
There’s a bucket of candy for developers as well, including our new Post Formats support which makes it easy for themes to create portable tumblelogs with different styling for different types of posts, new CMS capabilities like archive pages for custom content types, a new Network Admin, an overhaul of the import and export system, and the ability to perform advanced taxonomy and custom fields queries.
With the 3.1 release, WordPress is more of a CMS than ever before. The only limit to what you can build is your imagination.
By the Numbers
There were over two thousand commits to the codebase in the 3.1 cycle! For a more comprehensive look at everything that has improved in 3.1, check out 3.1’s Codex page or the more than 820 closed issues in Trac.
Error while installing SQL 2008 R2
You may receive the following error while installing SQL 2008 R2 edition on your system/server:
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly ‘System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′ or one of its dependencies. The system cannot find the file specified. (C:\Users\Administrator\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) —> System.IO.FileNotFoundException: Could not load file or assembly ‘System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′ or one of its dependencies. The system cannot find the file specified.
File name: ‘System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′
at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory..ctor(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
— End of inner exception stack trace —
at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
at System.Configuration.SettingsBase.SetPropertyValueByName(String propertyName, Object propertyValue)
at System.Configuration.SettingsBase.set_Item(String propertyName, Object value)
at System.Configuration.ApplicationSettingsBase.set_Item(String propertyName, Object value)
at Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings.set_WindowPlacement(WINDOWPLACEMENT value)
at Microsoft.SqlServer.Configuration.LandingPage.LandingPageForm.OnClosing(CancelEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
—————————————-
LandingPage
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///h:/9a123339f116b0007807ea/x86/LandingPage.exe
—————————————-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
—————————————-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
—————————————-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
—————————————-
Microsoft.SqlServer.Configuration.Sco
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///h:/9a123339f116b0007807ea/x86/Microsoft.SqlServer.Configuration.Sco.DLL
—————————————-
Microsoft.SqlServer.Chainer.Infrastructure
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///h:/9a123339f116b0007807ea/x86/Microsoft.SqlServer.Chainer.Infrastructure.DLL
—————————————-
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
—————————————-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
—————————————-
Microsoft.SqlServer.Management.Controls
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///h:/9a123339f116b0007807ea/x86/Microsoft.SqlServer.Management.Controls.DLL
—————————————-
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
—————————————-
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
Solution:
You can fix this problem by deleting \users\(your profile)\Local Settings\Application Data\Microsoft_Corporation\ folder. If you have older operating system, use “documents and settings” instead of “user”.
Kailash Aghera
-
Recommended Host
-
