Thanks for the prompt response!

Can you create multiple tokens from the same Ethereum address? I tried to create two tokens. The first one worked fine but the second one has been stuck at "Compilation Done, Sending for deployment...." for a few hours now. Another token was created during the that transaction was stuck from another address so I figured it must be a bug of some kind. The transaction ID of the stuck request is 0xe99b1aa28a6a06a3499e0f2f57b667cb32e91d29ec6eb23b145431767800a027

Don't use the web wallet if it is having issues on your end. You can set it up locally pretty easily:

Docker - https://lisk.io/documentation?i=lisk-docs/DockerInstall
Binaries - https://lisk.io/documentation?i=lisk-docs/BinaryInstall

Make sure to read the documents carefully. If you use Docker you have to SSH into the Docker instance before continuing to Step 2, so make sure to write the default Docker user/pass down so you have access to it:

SSH from terminal:
ssh docker@192.168.99.100

PuTTY (GUI SSH Client):
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

YOU'RE NOT MY MOM!  

You have what you paid for. Everyone that validated their exchanges before the cut off date has their Lisk in their account. If you cannot access any of the three official web wallets and cannot be bothered to learn how to set up a local node, or research any of the delegates posting links to their nodes to see if those nodes are safe to access, then that is a problem solely between the chair and keyboard.

The documentation is available and very thorough. Please take a gander at it.

Install via Docker (easiest) - https://lisk.io/documentation?i=lisk-docs/DockerInstall
Install via Binaries (more prep) - https://lisk.io/documentation?i=lisk-docs/BinaryInstall

The platform is targeted towards developers and now that it is live all the developers that were waiting for the mainnet to go live to test their apps have hit the ground running. The only people having trouble are the non-developers that are trying to use the web wallet to trade Lisk instead of develop with it, and yes on that front the Lisk team could have prepared better and at least set up a load balancer to intelligently distribute the traffic. Seeing as how it is live and developers can easily set it up and don't have to deal with the mess that is writing ETH smart contracts, yes it is very much a success.

I would be more than happy to build Virtual Machine appliances and Raspberry Pi 2/3 images for anyone that was having trouble getting it up and running locally if there is a market for it   . PM me if you need that kind of help.

Excellent! Glad to hear it all worked out. I would recommend not using Internet Explorer entirely and moving to Firefox and Chrome full time. Both browsers are faster and more secure.  

The wallet you were probably sending from was out of sync and the transaction did not complete properly. Try sending it again.

Make sure when you are sending your coins you are accounting for the 0.1 LSK transaction fee. So basically if you have 5.98 LSK then you can only send 5.88 LSK.

Yes. You can just log in, validate them, and then refresh and try a new one 

I'm going to grab some dinner. If it still doesn't work for you feel free to PM me and I can help walk you through it when I get back.  

Both wallets are loading correctly for me with correct balances. If you are copy and pasting your passphrase I would suggest to try loading your text file into a different text editor like Caret (http://bit.ly/1VhuL17) and to trim your passphrase and make sure there are no leading/trailing spaces.

Setting up a wallet locally and accessing the testnet/web wallet have been covered by Lisk in both the documentation and their blog which they also cross post to Twitter and Facebook. As many mistakes that Lisk made during the launch, and there have been a lot, they have been surprisingly good at staying transparent and creating extensive documentation.

Use the passphrase that you should have saved when your validated your purchased on the exchange. If you are using Windows then do not use notepad to get the passphrase as it messes up the encoding for most people. Try either dragging the text file with your passphrase into a browser like Chrome or Firefox, which should display it in the correct encoding, or use a text editor like Caret (http://bit.ly/1VhuL17). Your passphrase is case sensitive and it needs to be trimmed if you are pasting it in (trim means to remove and spaces before or after your passphrase/string)

It is possible it is still syncing. If it is you should see a circle with a value between 1-99 in the top right hand corner on a desktop browser.

RTFM and stop whining. You can easily build the wallet in a virtual machine, deploy it to a VPS, or deploy it to a Docker container. You do not need to log in you just have to use your eyes and read the documentation. If it is too hard for you then you should have researched what you were buying into before jumping in head first. It was clearly stated this was a platform targeted towards app developers and it has had an active testnet you could have deployed locally for months and been prepared for this.

Lol you do realize this is a platform for computer programmers, correct? 

If you have an extra Raspberry Pi laying around, use that. That is what did. I didn't want to deal with updating from the testnet so I just burned a new image of Raspian Lite, ran through the pre-setup scripts, and installed from binary. You can probably avoid the Raspberry Pi and just use a VirtualBox virtual machine and achieve the same results. Before getting upset remember that this is a platform that is being targeted at software/web engineers, so be prepared to get your hands dirty on day one. If you can't do that it's probably best to wait until someone puts together an easier method to get up and running

Technically if you can't Linux, doesn't that make you the noob?