SQL server in services.msc

MS SQL Server 2008 and getting access

Couldn’t get into a 2008 SQL server today, whoops!

No one had the credentials so I had to get myself access. I found an article covering adding yourself via single user mode, but thought I’d add some more details for my own information and to cover missing info on that page.

  1. Shut down any services related to SQL and anything that connects to it. The ones I shut down on the server side were:
    1. SQL Server VSS Writer
    2. SQL Server (MSSQLSERVER)
  2. Next step, start SQL in sngle user mode
  3. Eventually it’ll show that SQL server is running
  4. Start up another command prompt in Administrator mode, then run the following commands. Replace SERVERNAME with the local hostname, and username with your admin account username.
  5. Type “exit” and hit enter to close out of that SQL command line agent, then Ctrl-C in the SQL server window to shut it down.
  6. Start the server back up using services.msc.
Wireshark Running

Wireshark on OSX Mavericks

So, Wireshark in Mavericks doesn’t work terribly well. If you install XQuartz and the Wireshark application then try to run it, it’ll just sit silently mocking you in the Dock.

There’s a few steps. First you want to add it to the “Applications” menu on XQuartz. Run XQuartz and then right click on the icon, select Applications, then Customize…

editing applications in xquartz

Add a new item, and fill it out as below. This will allow you to run it from the XQuartz menu in future.

wireshark in xquartz

Just for testing purposes, I’ll show you what’s going wrong in xterm:

Wireshark in xterm

For some reason, XQuartz can’t display what it wants to, poor guy. The command to run is “export DISPLAY=:0″ and it’ll open any of the Wireshark windows you’re already running. To avoid this issue in future, what I’ve done is made a little script that automagically does that when you run Wireshark.

If you move the Wireshark binary (/Applications/Wireshark.app/Contents/MacOS/Wireshark) to Wireshark-bin, then create the following script in its place it’ll automagically run the export command on startup:

Make sure you go to the directory and run “chmod +x Wireshark” to allow it to be executable, and you’ll be fine to go.

If you’ve got Wireshark installed in another directory, ensure you update the paths appropriately.

I’m sure there’s a better way to do this, but … it worked for me :)

 

Cascade Shark not detecting new card

So I’m installing a new NIC-CSK-210G in my Cascade Shark 2100. It’d start up fine but the new card wouldn’t detect. The NIC-CSK-4TX-X installed detected fine, but the other one didn’t.

When going to the “Interfaces” screen on the WebUI, I’d get a weird error:

Please Wait... Cascade Shark is not quite ready. Retrying in a few seconds. Retry Now

If you waited a few seconds or clicked the “Retry Now” button, it’d log you out and kick you back to the login screen. Ugh.

While waiting for a case I logged with Support I decided to grep through the logs a bit Continue reading