Fix Word Document Cannot Open Error [Repair Assistance]

Word cannot open this document. The document might be in use, the document might not be a valid word document, or the file name might contain invalid characters.

If you’re receiving this error, send along your document to

and I will see if I can recover the text for you. If there is enough demand, I will build an online tool to recover documents from this error.

Filetypes receiving this error may include: doc, docx, msword, dot, dotx, rtf, docm, dotm

Amazon Seller Central Outage – 19 June 2017

Amazon has been experiencing an outage for Seller Central, today, 19 June 2017.

Sellers are reporting intermittent outages with seller tools such as the forums and FBA fee calculator, while the Seller Central platform seems to be completely down with sellers receiving the following messages:

Amazon Seller Central: Seller Central is Temporarily Unavailable, We apologize for the inconvenience. Our technical staff is working on a solution.
Amazon Seller Central: Seller Central is Temporarily Unavailable, We apologize for the inconvenience. Our technical staff is working on a solution.
Amazon Seller Central: Internal Error – The website is having a technical problem, please try again.

While Amazon’s AWS is showing no outages, Amazon still does not seem to have publically acknowledged the outage.


Common Firmware Environment CFE Commands

CFE> help
Available commands:

checkflash Check nand flash memory.
checkmem Check memory.
checkBC check the bootcode settings
show clocks Show current values of the clocks.
nvram NVRAM utility.
reboot Reboot.
tftpd Start TFTP server
flash Update a flash memory device
memtest Test memory.
f Fill contents of memory.
e Modify contents of memory.
d Dump memory.
u Disassemble instructions.
batch Load a batch file into memory and execute it
go Verify and boot OS image.
boot Load an executable file into memory and execute it
load Load an executable file into memory without executing it
save Save a region of memory to a remote file via TFTP
ping Ping a remote IP host.
arp Display or modify the ARP Table
ifconfig Configure the Ethernet interface
help Obtain help for CFE commands

For more information about a command, enter ‘help command-name’
*** command status = 0

Bitcoin Fork Plain English – UASF / BIP148 vs Segwit

SegWit is a movement among bitcoin miners to increase the block size from 1 MB to 2 MB (Megabytes). SegWit can be activated by the bitcoin miners collectively by the highest ratio of miners “voting” for it.

In addition to raising the blocksize, SegWit will also enable platforms to be built on top of the bitcoin network, giving it some of the malleability of the Ethereum network. The Bitcoin Lightning Network seeks to make transactions faster and more scalable on the blockchain, but will require SegWit to be activated by the miners. 95% of the miners must ‘signal’ their vote for Segwit in order to activate it.  As it stands, many miners are not signaling for SegWit activation – perhaps due to the change SegWit could bring to the ecosystem or due to the potential loss of profit from easier transaction transfers (and lower transaction fees).

UASF / BIP 148 is a blockchain user movement to change the bitcoin core code to deny blocks not signaling for SegWit. If all goes well, 100 block confirmations after BIP 148 implementation, SegWit will be force-activated on the bitcoin network. The force activation take place by bitcoin nodes and users signaling their support for BIP 148 and rejecting mined bitcoins without SegWit support. By activating via the nodes of the blockchain network (rather than the miners themselves activating it) the benefits of SegWit are brought to the blockchain without the need for 95% of miner support. Blockchain miners can also force this upgrade with 51% signaling support for BIP 148.

The problem: Before that 100th block is confirmed on the blockchain, there is a potential for the blockchain to diverge into two. With transactions and mining taking place separately on each blockchain two coins will be born out of one, akin to ethereum and ethereum classic.

According to reddit user luke-jr, we can avoid a chain split by:

  • 95% of hashrate locks-in segwit before August 1st. No chain split at all.
  • 51% of hashrate deploys BIP148 before August 1st. No chain split at all.
  • 51% of hashrate deploys BIP148 after August 1st. Chain split gets resolved.
  • Legacy miners are compelled by the economy to switch to BIP148 after Aug 1st. Chain split gets resolved.

It’s recommended to keep your coins in your own offline wallet during the change or to confirm with your online wallet their plans with your coins in the event of a split.




Cannot Sell This Reserved Instance

You may receive the following error message from AWS when trying to sell your reserved instance:

This issue is likely due to one of these two problems:

  • There was an error retrieving the selected reserved instances details
  • Failed to exchange reservation due to: Can’t exchange from non-convertible classic offering
  • You’re not a registered AWS instance seller, register here.
  • You’re trying to sell a Standard  EC2 Reserved Instance with No Available Zone Scope
    • Per Amazon’s Requirements: Standard EC2 Reserved Instances can only be listed in the Reserved Instance Marketplace, if they are purchased with an Availability Zone scope. Since capacity is not reserved with regional RIs, they cannot be sold on the Marketplace at this time.

If you’re a registered seller and you are still receiving this error, you may be stuck with this particular reserved instance.

Some notes about selling reserved instances:

  • Reserved instances can be sold after they have been active for at least 30 days and once AWS has received the upfront payment (if applicable).
  • There must be at least one month remaining in the term of the Reserved Instance you are listing.
  • You must have a US bank account to sell Reserved Instances on the Reserved Instance Marketplace. Support for non-US bank accounts will be coming soon.
  • You will retain the pricing and capacity benefit of your reservation until it’s sold and the transaction is complete.
  • Your company name (and address upon request) will be shared with the buyer for tax purposes.
  • A seller can set only the upfront price for a Reserved instance. The usage price and other configuration (e.g., instance type, Availability Zone, platform) will remain the same as when the Reserved instance was initially purchased.
  • The term length for a Reserved instance will be rounded down to the nearest month. For example, a reservation with 9 months and 15 days remaining will appear as 9 months on the Reserved Instance Marketplace.
  • You can sell up to $50,000 in Reserved instances per year. If you need to sell more Reserved instances, complete the form found here.
  • Reserved instances in the GovCloud region cannot be sold on the Reserved Instance Marketplace.
  • Reserved instances purchased as part of a tiering discount cannot be sold in the Reserved Instance Marketplace.


pdfsizeopt – AssertionError: Multivalent failed (status)

This error could mean you’re using a  newer version of Multivalent which no longer has the pdf tools bundled into it. You’ll need this older version with the proper tools.

Download: Multivalent.jar

Just as a note though, pdfsizeopt is a pretty old program that may not be able to handle newer pdfs and may do a poor job optimizing many others.


File “./pdfsizeopt”, line 30, in <module>
File “./lib/pdfsizeopt/”, line 8081, in main
is_flate_ok=not do_decompress_flate)
File “./lib/pdfsizeopt/”, line 7773, in Save
File “./lib/pdfsizeopt/”, line 7691, in _RunMultivalent
assert False, ‘Multivalent failed (status)’
AssertionError: Multivalent failed (status)

/usr/bin/java -cp /users/lukerehmann/Multivalent.jar -Djava.awt.headless=true tool.pdf.Compress -nopagepiece -noalt -mon ADTTD_Product_Manual-Approved_Labeling_optimized.pdf
Exception in thread “main” java.lang.NoClassDefFoundError: tool/pdf/Compress
Caused by: java.lang.ClassNotFoundException: tool.pdf.Compress
at Method)
at java.lang.ClassLoader.loadClass(
at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(

Google Cloud : Service account not enabled on this instance

PHP Fatal error: Uncaught exception ‘Google\\Cloud\\Core\\Exception\\NotFoundException’ with message ‘{“error”:”invalid_request”,”error_description”:”Service account not enabled on this instance”}’ in /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php:241\nStack trace:\n#0 /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php(150): Google\\Cloud\\Core\\RequestWrapper->convertToGoogleException(Object(Google\\Cloud\\Core\\Exception\\NotFoundException))\n#1 /var/www/html/vendor/google/cloud/src/Core/RestTrait.php(86): Google\\Cloud\\Core\\RequestWrapper->send(Object(GuzzleHttp\\Psr7\\Request), Array)\n#2 /var/www/html/vendor/google/cloud/src/Storage/Connection/Rest.php(132): Google\\Cloud\\Storage\\Connection\\Rest->send(‘buckets’, ‘insert’, Array)\n#3 /var/www/html/vendor/google/cloud/src/Storage/StorageClient.php(225): Google\\Cloud\\Storage\\Connection\\Rest->insertBucket(Array)\n#4 /var/www/html/gcloudtest.php(20): Google\\Cloud\\Storage\\StorageClient->createBucket(‘my-new-bucket’)\n#5 {main}\n thrown in /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php on line 241

The FuzeCard Problem – EMV Chip Payments and Bank Negotiations

In the past couple years, we’ve seen the coming and going of several smart card companies promising to merge all your credit, debit, and rewards cards into one smart connected wallet. Despite the excitement surrounding all these products, they seem to run into one common wall when it comes to consumer deployment – EMV “Chip” Payments.

Coin and Plastc Shutdown, leaving millions of backers (and their money) out to dry. While Stratos and Swyp seem to be in a perpetual “sign up to get notified” phase. None of the cards have ever successfully supported Chip and Pin or EMV Payments. Why? Because it requires big connections and a large customer base to convince banks to open up their secure chip and pin technology to your ‘smart card’, and, unfortunately, this requires negotiations with each card issuer.

From FuzeCard’s website:

EMV payments require the approval of the card issuer/banks. Fuze’s chip will be compatible from the launch and this feature will be fully available with a future firmware update

As promising as this may sound, it’s not a software problem that Fuze is up against here and no simple firmware update will give the card the EMV support it needs. BrilliantTS will need to first negotiate with big banks, and that’s a tough sell at least 4 companies have failed to do thus far.

Do their promo cards have working EMV chips? According to their Instagram content, no, not yet.

One post from their instagram shows a box of bpay cards from a startup in South Korea. So, what do bpay and FuzeCard have in common? Both appear to be owned by BrilliantTS.

BrilliantTS’s bpay cards appear to have come to the same brickwall for EMV Payments, indicating only “Reserve Now!” for EMV Chip enabled cards.

bpay Card Options