SSRS 2016 Mobile Report Publisher Error 500

Hi All,

So In case you struggle as I was with SQL Server 2016 Reporting Services and specifically I had two issues:

• SRS website simply will not show any content which I ignored at start with some similar 500 Error
• Then when I tried to use Mobile Report Publisher I saw this 500 error

In the SRS logs ("C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles" in my case) I can see something like that

Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!fe!06/20/2017-12:13:09:: e ERROR: [frrma4f2]: OData exception occurred: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentOutOfRangeException: The UTC time represented when the offset is applied must be between year 0 and 10,000.

Now you have to remeber words OData and the string about UTC time.

Turned out the issue is with the fact that... wait for it... your server is living east of London :)

Reset timezone to EST (GMT with minus "-", to the left, west side :)) and the error is gone

I mean, Microsoft, really? :)

I was able to find a solution from this blog post
https://morgansimonsen.com/2015/12/07/office-365-hybrid-configuration-wizard-fails-due-to-datetime-minvalue-issue/
Which is about a problem in C# reported here, a problem known in 2012!!!

Hope this helps someone else out there :)

Win8 WiFi "limited" issue and old DLink router

Hi,

You all probably already saw a lot of different fixes for the "limited" WiFi in Windows 8. TCP/IP stack reinstallations, WiFi network re-adding and many more. Well, they didn't work for me.

The reason for my troubles was DHCP from my old Dlink router. For some reasons when my router were allocating addresses dynamically with pre-set lease time, my Win8 devices were loosing connection from time to time and WiFi state were switching to "limited" state. A workaround was to restart the router, this worked for me, but then I decided to understand the source of the problem.

It turned out that DHCP renew command didn't work. My thought is that my old router has its own internal sense of current date, time and timezone :) I didn't need to fix that because my router is not a time source. And I think what is happening is that the router had it's own sense of lease time and its own sense of when IP address is expired or not, probably this doesn't work well with Windows 8.

To fix that I've added fixed, static DHCP mapping for Windows 8 devices and it worked! Now I don't have issues with Windows8 WiFi devices and I don't need to change my router (originally I thought it's a bug in the firmware and due to my router being too old I thought I had to change it)

Incorrectly flashed atmega328p back to life

Hi,

I'm new to microprocessor programming and all the related stuff (bootloaders, fuses, ISPs, etc.), so I faced a newbee issue.

Symptom:

I was trying to flash atmega328P with bootloader that will suport 8MHz internal clock (so that I don't need an external oscillator) and can be futher optimized in terms of power consumption. I did everything correctly in terms of wiring USBasp programmer (I was using the following instructable), but then unintentionally (I just knew that LilyPad bootloader would also work) I programmed LilyPad's bootloader which also means LilyPad's fuses, which also means (as I later discovered) usage of external oscillator (nice tool to decode fuses).

So, that brought me all the way to "Yikes invalid signature 000000" with usage of -F option in avrdude, or "avrdude: error: programm enable: target doesn't answer. 1" without it. Different "-B" options (-B250, -B5, etc.) didn't work for me. Chip is just completely silent.

And also "avrdude: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xfc" when I try to talk to the MCU via Serial ports with help of FTDI chip. At least I could see that chip is not dead comletely, it's replying something. Probably abrakadabra and maybe it could be decoded by using a proper avrdude settings, but I tried different baud rates and other settings and nothing worked.

Cause:

MCU just expect an external clock source and just doing nothing without it.

Resolution:

Connect an oscillator. But what if you don't have a spare one? Do it like me:

This is a wireless NRF24L01 board and it has an oscillator on it, just connect board ground (yellow on the photo and PIN1 on this wireless board) to your MCU ground and oscillator lines (green and white) to PIN9 and PIN10 on your atmega328P.

This fixed everything for me, Chip is alive and I can see all fuses, so I was able to reprogram them.

Although it's a little bit ackward - because oscillator is 16Mhz and LilyPad bootloader expects 8Mhz.

Hopefully this post will save some time for someone who faced the same issue.

UPDATE:
Looks like this is only a one part of the puzzle, the other one is protocol issue which I also mentioned above, it is still present after a correct bootloader is flashed.

Apparently the issue is with not very accurate internal oscillator - it just doesn't work with high baud rates for programming. There is a very good and detailed explanation on how to fix this by re-compiling a bootloader to use slower upload speed, I do not have necessary tools to do that, so I do think I'm going to do that, I think for me it's OK to load firmware via the ISP

I was able to confirm that it's working and chip is perfoming properly using its internal oscillator. Then I can install a code that will programmaticaly set slower baud rate if I need to talk to the firmware onboard the atmega chip.

Uploading Arduino .hex from Netgear Stora

AAAAAAAAA

I've done it. After so much pain. I even do not remmeber all the steps. However:

• I've compiled usb drivers and ftdi drivers. I have a post about it 
• I've compiled avrdude 6 on my Netgear Stora. Don't ask how. There was also a lot of pain. But for some reason avrdude 6 worked while v5 still cannot be compiled.
• I have a daemon which talks to arduino, so to program I have to switch it off
• Then I faced an issue whatever I tried I receive "avrdude: stk500_getsync(): not in sync". Looks like the issue was with my usb and ftdi drivers - for some reasons they can't help avrdude to negotiate a correct baudrate for my arduino. I tried several and looks like 57600 worked for me. I tried terminal mode like this

/root/avrdude-6.0.1/avrdude -t -v -v -v -v -c arduino -p m328p -b 57600 -P /dev/ttyUSB0

• But then another issue arised - looks like core version of avrdude cannot properly reset the arduino. There are several tricks on how to do that manually - I'll try them later. Also I think Arduino's version of avrdude can do that, but I have issues compiling it on my Netgear (some Perl issues - nothing too serious can be solved in the future). So I went with another solution - I just reset my USB subsystem and then attach to arduino to upload a sketch. To reset the usb subsistem I'm doing the following:

echo -n "1-0:1.0" > /sys/bus/usb/drivers/hub/unbind

echo -n "1-0:1.0" > /sys/bus/usb/drivers/hub/bind

•  In the above code IDs of your USB hub could be different, so check them in the folder /sys/bus/usb/drivers/hub/, but I guess on all Storas they should be the same.
• Then upload the sketch, like that:

/root/avrdude-6.0.1/avrdude -v -v -v -v -c arduino -p m328p -b 57600 -P /dev/ttyUSB0 -D -Uflash:w:/home/arduino/Firmw4_4.cpp.hex

Have a good time with your IoT ;)

Low power wireless sensor node, using stock arduino

Hi ardu-people,
There are a lot of posts in the Internet about making a low power arduino projects. However most of them assume you have to do it with custom built arduinos using atmega chips, I think it’s a correct approach, BUT it is still possible to do a low power node even on stock parts. Below are some hacks I discovered or confirmed while creating my low power projects.

• LED lights
  There are a lot of articles about how much power do they really consume and I can only confirm that, even this tiny power led on your Pro Mini or Nano. I used sharp knife to cut the connection to the power led on my Pro Mini and I desoldered leds on all other peripherals such as radio power converter
• Power down mode
  For my arduino I was using Narcoleptic library, and PowerDown mode for the nrf24l01 radio. For arduino everything worked perfectly, for radio see below
• Cut power to peripheral devices
  To save some more power we can disable sensors while arduino and radio are sleeping, simple solution is to power up sensors using arduino pins, set pin to HIGH to enable device, LOW to power it down, this worked perfectly for me. If you see issues with measurements, you may need to add a delay after powering a sensor up. More appropriate solution is to use tip120 or something similar to disable/enable power for all sensors at once.
• Radio nrf24l01 power down issues
  Unfortunately looks like Nfr chip doesn’t like power manipulations, after several cycles of powering it down with arduino pin as a power source as per above while radio is in the powerdown mode, the radio developed some kind of a power leak and started to consume more (~6ma). Radio is functioning properly, but consuming a lot for a sleep period. I’ve understood that it’s consuming power via MOSI line (pin11), the solution was to set all nrf pins to low and to switch MOSI pin to input mode, don’t forget to switch it back to output when powering everything back up.

Stay tuned, I’ll be working with reducing power consumption with relays, coz they are eating a LOT

Written with StackEdit.

error expected '=', ',', ';', 'asm' or '__attribute__' before

Compiling avrdude on ARM Netgear Stora to be able to work with and program Arduino board.

Solved a lot of other quite complicated dependency issues, had to compile some of dependencies myself and then stuck with this error in the subject for almost half a day.

error expected '=', ',', ';', 'asm' or '__attribute__' before

WTF!
I had 'OD' symbos in the beginning of the .c file which had includes to the .h files which failed with the error. OMG, how the hell on earth did it get there?

Anyway, for those who find my post - check the source file which has includes to the header files which are failing, then check preceeding code - something is already wrong when compiler goes into the header files.