VirtualBox Error: Kernel driver not installed (rc=-1908)

 
VirtualBox merupakan aplikasi komputer secara virtual. Jika pada saat akan menjalankan suatu sistem operasi dengan VirtualBox, terkadang muncul dua pesan error pada dua kotak dialog. Pesan error pertama yaitu:

Failed to open a session for the virtual machine winxp.
The virtual machine ‘winxp’ has terminated unexpectedly during startup with exit code 1.

Lalu saat mengklik detail akan muncul pesan:

Result Code:
NS_ERROR_FAILURE (0×80004005)
Component:
Machine
Interface:
IMachine {6d9212cb-a5c0-48b7-bbc1-3fa2ba2ee6d2}
Lalu pada kotak error dialog kedua muncul pesan:

Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
‘/etc/init.d/vboxdrv setup’
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

Untuk mengatasi masalah tersebut, konek ke internet lalu buka terminal. Pada terminal ketikkan perintah berikut satu persatu:

Unable to Browse The Cube in SQL Server 2000 Analysis Services

Some users may have same problem. You have just installed Analysis Services, and were able to build and process cubes, however, unable to browse cubes. When you tried to browse the cube by right clicking on a cube and selecting the option 'browse data', an error message came up: 'unable to browse the cube, unspecified error'. Sometimes the error message contains an additional line 'unable to locate the cube'. You may checked the data path in the Server Properties and it is correct. Commonly, it could be that the SP3 for Analysis Services might not have been installed.

These are the alternative steps may useful to solve your problem.

1. Download the file sql2ksp3 from http://www.4shared.com/get/BaKvLtR4/sql2ksp3.html
2. Extract it. The location should be in drive C:\sql2ksp3 
3. Rename the old msolap80.dll (precaution only) to msolap80.dll.replace (location should be something like:  C:\program files\common files\system\ole db)
4. Rename old msolap80.rll (again precaution) to msolap80.rll.replace (location should be something like: C:\program files\common files\system\ole db\resources\1033
5. Copy msolap80.dll from c:\sql2ksp3\x86\system (SP3 file folder) and paste into folder under step 3.
6. Copy msolap80 from c:\sql2ksp3\x86\system\res\1033 (SP3 file folder) and paste into folder under step 4.
7. Reprocess cube and view using browse data.

Please try it!

Postgres ODBC, Linked Server, SQL Server Reporting Services Connection

Connect to Postgres using ODBC connection follow these steps:

1. Download Postgres ODBC driver from http://www.postgresql.org/ftp/odbc/versions/msi/ 
2. Install above ODBC drivers
3. Create system DSN ... On windows XP > Control Panel > Administrative Tools > Data Sources (ODBC)
4. Go to System DSN Tab > Add > Select PostgresSQL Unicode sriver > Finish
5. On Prompted page add

Data Source --- Whatever you want to name the DSN
Database - Name of postgres database
Server - Name of Postgres server
Port:5432 (or whatever you database port is..)
Username and Password: Enter postgres database username /password you wish to use

Test the System DSN by clicking on Test

• Create Linked Server on SQL Server 2008/2005 to connect to postgres database

Start SQL server management studio
Connect to SQL server instance where who wish to create linked server
Go to ServerObject > linked Servers > New Linked Server
Fill the Linked server properties

Select Provider: Microsoft OLEDB Provider for ODBC Drivers
Product name: postgres (you can put whatever you like)
Data Source: Name of System DSN created in last step

Right click Linked Server and Test Connection
Now you query postgres from SSMS by something like

How to Restore Ubuntu Grub Bootloader after Reinstalling Windows

If you run a dual-boot system with Linux and Windows, this has happened to you. You had to do your monthly reinstall of Windows, and now you don’t see the linux bootloader anymore, so you can’t boot into Ubuntu or whatever flavor of linux you prefer.

Here’s the quick and easy way to re-enable Grub.

1. Boot off the LiveCD
2. Open a Terminal and type in the following commands, noting that the first command will put you into the grub “prompt”, and the next 3 commands will be executed there. Also note that hd0,0 implies the first hard drive and the first partition on that drive, which is where you probably installed grub to during installation. If not, then adjust accordingly.

sudo grub
> root (hd0,0)
> setup (hd0)
> exit

Reboot (removing the livecd), and your boot menu should be back.

Only read below if Windows is now missing from the boot menu