Quick Tips

A little something about everything

internet marketing and website development made simple..

Cannot find the certificate request associated with this certificate file. A certificate request must be completed on the computer where it was created.

Error:

Cannot find the certificate request associated with this certificate file. A certificate request must be completed on the computer where it was created.

Issue,

The certificate is still being processed and has not yet been added to the server.

Resolution

Click ok and wait

After waiting refresh (F5) the certificate window within IIS.

You will notice that the SSL certificate is missing a friendly name, in order to fix this you can do the following.

Start > RUN > type in mmc and click enter

Click File Add/Remove snap-in

Double Click Certificates > Computer account then next, Local computer then Finish, OK

Browse to Personal > Cerfificates then right click the new certificate and click properties, Enter a Friendly Name and click OK.

You can close all windows now.

How to recover serveradmin access of teamspeak3/ts3 server after system reload.

This works but you should still stop and backup your ts3 server.

After you backup is complete follow these steps.

While ts3 server is stopped start the server using this command: (assuming you are running 64 bit server on windows)

(Drive):\Path\ts3server_win64.exe serveradmin_password=YourNewPassWord

(You can do this by making a shortcut and editing the target location as well)

Now you have an updated TS3 admin password, with this you can create a new privileged key.

Using puttytel.exe or any other telnet client to type the following commands:

(localhost if your server is hosted on the pc/server you are running telnet on, otherwise just use the ip or server name)

After the last command the server will respond with a token=YourNumbersAndLettersToeknID

Copy this and past it into your TS3 client under permissions > use privileged key.

Moving database from MS SQL 2000 to 2005 or 2008 | Error / User / Roles / Delete

In order to fix this bug you can simply run this command on the effected database after you have used the backup (sql2000) / restore sql2005/2008) or detach attach methods.

command to run:

 

Replace "dbusername" with the problem user account. both should be the same.

This will remove the ghost user from the sql 2000 server and replace it with the new user on your sql 2005 / 2008 server. Be sure to have the user created before running this command.

Errors associated with this are as follows:

"login name must be specified Database user"

"The database principal owns a schema in the database, and cannot be dropped"

"user group or role already exists in the current database"

"can't delete sql user in database"

The network folder specified is currently mapped using a different user name and password. To connect using a different user name and password, first disconnect any existing mappings to this network share.

To disconnect from a ghost or rogue network path do the following:

  • (Open cmd.exe)
  • net use /delete \\(computername)\(sharename)

To disconnect from a ghost or rogue network drive do the following:

  • (open cmd.exe)
  • net use (diveletter): /delete