Windows blue screen fix

This is in response to an email I got asking me about how my upgrades went and if I used new hardware.
-----------------------
When we did our big upgrade to 6.3.8, we moved the database to new hardware and then did the upgrade.
We also had a consultant do the conversion because we moved from Oracle to SQL server.
The conversion went fine. I move copies of the database to my test server all the time. Moving the databases around is no problem since there is no software tied to it directly on the DB server.
I use Microsoft DFS that comes with Server 2003 R2 and beyond to create DFS shares for my visual files. That way I can move servers around and it will not ever break Visual on the desktop.
So my Visual binary files are always loaded from v: and the custom reports from o:.
I also have 3 sites with a WAN, so I use thin clients at the remote sites and a terminal server here connected to my DB server with a Gigabit line. It works great. Much better than running over the wan with just the Visual client.
Even my planners at remote sites use Remote Desktop to run Visual.

Back to the install…
It much easier to do smaller upgrades, so I have done the last 2 by myself.
Like from 6.3.8 to 6.4.1 and then I went from 6.4.1 to 6.5.1.
I upgrade Visual about once a year.
Both upgrades were very simple and the database changes were done in like 15 minutes or less.
I used to use Microsoft SMS 2003 (System Management Server 2003) to push out the software to the desktops, but it was just getting out of hand, so now I run everything from a network share and it seems to be fine.
We have about 50 concurrent Visual users and about 20 barcode stations.

I hate SQLbase. I have to use it for my some of my timekeeping software.
I use Microsoft SQL server 2005 now and it comes with Reporting services free and we use it for lots of custom web based reports. I love it.
The only thing I didnt like was that I had to re-create all my 100 users when I upgraded from SQL2000 to SQL2005. This also happens when you change servers, so I did both things at the same time, so that I would only have to re-create everyone once.

My Windows Phone 8 OS-Version: 8.10.12397.895 startet to throw error 86000106 when syncing with my companys Open-XChange groupware server.

Found similar issues described in a forum, but that did not help for me:

http://answers.microsoft.com/de-de/winphone/forum/wp8-wpemail/fehler-bei-active-sync-fehler-86000106/a69fb145-29d2-4c12-8730-7ecbd389787e?rtAction=1404212848646

https://mailbox.org/windows-phone-8-1-fehlermeldung-beim-synchronisieren/

The fixes suggested to change sync interval from "based on usage" to "manual".

How-I-fixed-it:
I deleted the particular Exchange ActiveSync Account on my phone and added it again. The account syncs OK since this.

In my SQLCLR C# Stored Procedure on SQL Server 2008 R2 i returned the results using a SqlDataRecord that has a column of SqlDbType.Float.

Trying to set the value using the SetFloat Method, i got an InvalidCastException.

How-i-fixed-it:
I found out that SqlDbType.Float is equal to a System.Double data type. Using the SetDouble Method it works fine.

Here i found the right hints:
http://msdn.microsoft.com/de-de/library/vstudio/system.data.sqldbtype(v=vs.80).aspx

http://msdn.microsoft.com/de-de/library/vstudio/microsoft.sqlserver.server.sqldatarecord.setfloat.aspx

http://msdn.microsoft.com/de-de/library/vstudio/microsoft.sqlserver.server.sqldatarecord.setdouble.aspx






 



 

I recently updated to Visual Studio 2012 Ultimate.
When i tried to open an existing SQL Server SQLCLR Project (*.sqlproj), it says that the sqlproj is incompatible with the version I am running.

How-i-fixed-it:
I installed the SQL Server Data Tools from http://msdn.microsoft.com/en-us/data/tools.aspx.

I found the solution here:

http://stackoverflow.com/questions/11906691/visual-studio-2012-csproj-and-sqlproj

and here:
http://www.comoke.com/index.php/2012/10/visual-studio-2012-database-project-sqlproj-project-type-not-supported/

and here:
http://blog.tentaclesoftware.com/archive/2013/02/11/visual-studio-2010-and-2012-sqlproj-interoperability.aspx

I have a SIMULINK model to filter and process sensor data. I wanted to access some of model data from MATLAB workspace while the model was running.

How-i-fixed-it:

In my simulink model i added a non-blocking UDP receive block, a triggered subsystem ad a UDP send block.
The Status output of the UDP receive block triggers the subsystem which contains the UDP send block and received as Input the model data i want to send to the workspace.

In the workspace i create a UDP object to communicate with the UDP blocks in the SIMULINK model.
When the model is running, i send just a single byte on UDP from Workspace to the UDP Receive to Trigger the send. Next step is to read the desired number of bytes from the udp port in the workspace.

I found out, that the timing of this solution is not very performant. When the model is very busy (or at least the CPU is), then there can be significant delays in the model sending out the data on UDP. I think this does not work for real-time Systems, but its a simple solution to get it working.

I got a LateX document template that was using the bibunits package to create the references list. Out of the box, TeXnicCenter was not creating the references list in the document, there were still "unknown references".
How i fixed it:
I found the right hints here: http://latex-community.org/forum/viewtopic.php?f=50&t=9168&p=74542
There are two steps to make it working:
1. In your project folder create a batch-file with the following Content (in case its not already part of the template files):

@echo off
echo Processing auxiliary files with BibTeX
For %%i in (*.aux) Do bibtex %%i

save it e.g as compilebib.bat.
2. Then click define output profiles (Alt+F7), select the postprocessor tab, and add new. Put compilebib.bat under executable.

Today i was looking for a way how to sync my Outlook calendar with my doodle polls. I did a little search on Google and I exactly found what i was looking for:
The Doodle Outlook Connector: http://www.doodle.com/about/doodleOutlookConnector.html which works for Outlook 2007 and 2010 on Windows.

Description:
Start and answer meeting requests directly in the calendar interface. Your answers are automatically synched with your calendar

After TechEd 2014 North America I decided to test out Azure Active Directory Single Sign-On with Box.com.  I already had ADFS setup for Office 365, so it seemed a no brainer to try it out.

When I went to Azure.com I had to setup a new account (That came with a trial $200 credit for the first 30 days).
Even though I already had office365 and Azure AD setup and running, I still had to create a new Azure account before I could see it.  Azure AD just showed up after my first login, I didnt have to do anything special.  I found it funny that when I asked about this at TechEd, the people from the Office365 booth and the guys in the Azure booth didnt know for sure if it would just show up or not.

On to setting up Applications with Azure AD with box.com




They offer two types of Single Sign-On with Box.com.
1. Windows Azure AD Single Sign-On
2. Password Single Sign-On


Password Single Sign-On works fine, but if you want more advanced functions, like creating box.com users with Azure, then you want the Windows Azure AD Single Sign-on option.

It will give you a file called FederationMetadata.xml
When I contacted Box.com about importing this, this was the reply I got:

HI Ed -

Thanks for clarifying. So for set ups like this we recommend our program called Quick start. Here is a link to the description https://cloud.box.com/s/7kucoccfw8hybfrzxfs2


Melanie

Does anyone know if you really have to pay $1000 to get this setup or are they just pushing their consulting services?
The form Box linked to was for their consulting services that you might want to buy if you have not setup box yet.  I already have, so this seemed a little pointless to me when all I need was for them to upload the stupid xml file into their system.

Blue Screen of Death is a problem that often - often encountered in Windows XP operating system. Perhaps many thought when a computer is exposed to the BSOD we need to reinstall the operating system and some have had to buy a new computer. whereas many ways to fix the BSOD. Although usually BSOD problems most often encountered in the software, but there are less problems in the hardware related BSOD. And maybe this is some of my tips to avoid BSOD:


1.Check that minimum amount of free space available on your Windows partition (C :) is usaually. Blue Screen of Death can happen if there is not enough free space on your Windows partition.

2 Run anti-virus and anti-spyware. You should run your Adware program to check that your computer is clean of adware or spyware Some viruses can cause a Blue Screen of Death, especially those that infect the master boot record (MBR) or boot sector. Anti-virus software you have to be up to date at all times.

3.Update Windows. Microsoft released patches and service packs for the operating system they may contain fixes for the cause of the Blue Screen of Death. Missing updates can be a source of error stopped.

4.Check driver. Update drivers for your hardware, because of the high percent of Blue Screens of Death is a hardware or driver related so that a driver update can fix the cause of the STOP error. If you have recently updated a driver, you may be able to use the driver rollback to return to the previous driver version.

5.Return hardware settings to default in the Device Manager. Unless you have a specific reason to do so, the system resources that a single piece of hardware is set up to use the Device Manager should be set to default. Non-standard hardware settings can cause a Blue Screen of Death.

6.Check BIOS. Load BIOS default values​​. One of the BIOS settings can cause resource conflicts and timing issues. Maybe you need to update the BIOS after adding new hardware can help to fix your PC. A BIOS overclock or not properly configured can cause all kinds of random issues, including BSODs. In this case you need to revert to the default BIOS.

7 Repair your Windows Registry. Run the registry cleaner software to scan the registry, and fix errors. Blue screen error can be related to Windows registry problems. Blue Screen of Death can be caused by, invalid registry entries that are broken and dangerous.

8.Check all internal cables, cards, and other components. They need to be installed and seated properly. Hardware that is not securely in place may cause a Blue Screen of Death so try reseating the following and then examine the STOP message again:
Replace all internal data and power cables
Replace the memory module
Replace any expansion cards

9.Run memory test to check your computers RAM. Memory errors can cause a BSOD, so see if your RAM is error free. Vista and Windows 7 have a built-in option to test memor