You can Google this to find working tutorial of the above but I’ll try to make this short and direct to the point. You should have installed by now the Apache2.2.x HTTP Server with OpenSSL version for Windows on your server. If not,

  1. Download and install Apache2.2.x HTTP Server with OpenSSL version for Windows.
  2. Copy libeay32.dll and ssleay32.dll to your C:/WINDOWS/system32 folder. Usually the files are located in the /bin directory of your installation.
  3. Download openssl.cnf from neilstuff.com and place it where openssl.exe is located. Usually in the /bin directory.
  4. Create self-signed SSL
    • Open a command prompt in the directory where you openssl.exe is located (/bin folder).
    • Generate a CSR
      openssl req –config openssl.cnf –new –out –server.csr –keyout –server.pem
    • Create the key
      openssl rsa –in server.pem –out server.key
    • Create the cert
      openssl x509 –in server.csr –out server.crt –req –signkey server.key –days 365
  5. Enable SSL in Apache2.2.x
    • Open conf/httpd.conf and uncomment the line that loads mod_ssl (LoadModule ssl_module modules/mod_ssl.so), and the line which loads the httpd-ssl.conf file (Include conf/extra/httpd-ssl.conf).
    • Open conf/extra/httpd-ssl.conf and change VirtualHost settings (DocumentRoot, ServerAdmin, ServerName, ErrorLog, TransferLog). Also, change SSLCertificateFile and SSLCertficateKeyFile to point to your .crt and .key files.
  6. Restart Apache

When creating publication in a merge replication in MSSQL Server 2005, especially for beginners, it’s not new that while doing it in SSMS, you run into steps that makes your publication incorrectly configured thus forcing you to abort the process. Now when you cancel the publication and you’re in the middle of generating the snapshot, this could potentially harm your data and even your system. In my case, I tried to undo everything, did a cleanup, run the sp_removedbreplication and even tried to detach and attach the database just to make sure all processes orphaned to that database will be gone but I had no luck. After some time, it always gives me this message:

Another snapshot agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent

I have searched for solutions in MSSQL forums and documentations but I cannot find any. To my desperation, I tried to look on the properties of the job that’s being created in the process above and changed the account that run the snapshot agent associated to it to SQL Agent and that solved my problem. I spent too much wasted hours on this and wanted to share how I worked around to find the solution.

Hope this will help those who had the same experience with mine.

The process in creating Oracle linked server on a 64-bit SQL Server instance should be:

  • Install Oracle 10g Release 2 64-bit client software (available from Oracle website)
  • Install Oracle 10g Release 2 64-bit ODAC software (available from Oracle website)
  • Restart SQL services
  • Configure OraOLEDB.Oracle under \Linked Servers\Providers in SSMS in its properties making sure that “Allow inprocess” is enabled
  • Create the linked server
  • Test it

If you still can’t figure out how to do the above, see detailed step here http://www.mssqltips.com/tip.asp?tip=1433

For some reason that you receive an error trying to configure distribution on your MSSQL Server 2005 cluster and it will ask you to use the actual server name when connecting to the server, verify that your server name in the sys.servers catalogue is the same as your instance name. To verify, while connected to the SQL Server instance issue this in SSMS:

SELECT * FROM sys.servers

If the server name does not reflect the name of your clustered instance, rename it by dropping the old name and adding the corrected name. Drop the incorrect server name by this command

sp_dropserver @server='SERVERNAME_INCORRECT'

Then add the new and correct virtual server name as

sp_addserver @server='SERVERNAME_CORRECT', @local='LOCAL'

Then restart SQL Server service and replication should work fine.

This happens when the shared drives/LUNs in the cluster are not included in the dependency of your SQL Server resource. To fix this issue, go to SQL Server resource in the cluster’s SQL Group and go to properties. Under Dependency tab, modify it to include all the resources you wanted to be visible within your SQL cluster installation. Save your changes and you should be able to now see the shared drives in the cluster from within SQL Server.

This happens when you delete subscription and publication directly from Replication node in SSMS tool. Run below against the database you deleted the replication before setting it up again.

USE [database]

EXEC sp_removedbreplication

GO

By default, mcrypt is not loaded in PHP that comes in Snow Leopard fresh install. This tutorial will come handy when you don’t want to completely recompile PHP.

First, you may need an administrator account like root to execute below. When enabling the root account, make sure you know what you’re doing. It’s not a good practice to enable it. You need the following:
1. libmcrypt-2.5.8, which you can pick up here
2. PHP 5.3.0 source, which you grab here and
3. Xcode 3.2 tools, from the Snow Leopard installer

Next, create a /src directory in root and place the downloaded files. Move to the libmcrypt-2.5.8 directory, and type in this …

MACOSX_DEPLOYMENT_TARGET=10.6 CFLAGS='-O3 -fno-common -arch i386 -arch x86_64' LDFLAGS='-O3 -arch i386 -arch x86_64' CXXFLAGS='-O3 -fno-common -arch i386 -arch x86_64' ./configure --disable-dependency-tracking

Next, type in …

make -j6

Then finally …

make install

Libmcrypt is now ready. Proceed with configuring PHP.

Move back to /src, then down to php-5.3.0/ext/mcrypt – type …

/usr/bin/phpize

Then configure as

MACOSX_DEPLOYMENT_TARGET=10.6 CFLAGS='-O3 -fno-common -arch i386 -arch x86_64' LDFLAGS='-O3 -arch i386 -arch x86_64' CXXFLAGS='-O3 -fno-common -arch i386 -arch x86_64' ./configure --with-php-config=/Developer/SDKs/MacOSX10.6.sdk/usr/bin/php-config

make -j6

make install

Rename /etc/php.ini.default to /etc/php.ini. Edit it and ensure that enable_dl = On but do not remove the ; from in front of ;extension_dir = "./". Add one line to the .ini file in the Dynamic Extensions section… extension=mcrypt.so

Save your /etc/php.ini and restart Apache. You should be all set. Verify using phpinfo().

For MacPorts users, there is a good tuts here.

iMac

I’m glad that Macs are lowering their cost of ownership even if its computational power and features are just superb. This means that a lot of us now can justifiably own a Mac. In Cebu, Macs are still expensive gadget to own but for those who would like to be ahead in technology it’s worth an investment.

You can shop online here for cheaper Macs, way cheaper than iStore Cebu. And for the rest of your needs learning how great a Mac is, visit iShop store in Basak Mambaling, Cebu City.

Accessing the root account is disabled by default in Snow Leopard. Enabling the root account can leave your Mac vulnerable to security threats. Only enable it if you are aware of the risks and know what you are doing. If you do need to enable it, the terminal provides a simple solution that appears to work in 10.6: sudo passwd root. Enter your admin user password, then it will ask for a new password for root, and you’re done.

top