My congressional representative is Brad Miller. He’s done some great work and is generally well liked by his district. However, just like many Democrats this year, he’s facing stronger competition than in many previous years. Luckily, his opponent is a crazy conspiracy theorist (BP Truther) and “tea party” candidate.
I went to a house party for Miller’s campaign. This is the first time I’ve done such a thing. I’m always pretty politically motivated, but as far as campaigning goes, I’m usually just a money donator, bumper sticker/yard sign poster, and not much more.
The house party was encouraging. There were quite a few disappointed progressives, but they were largely positive towards Miller and more critical of Obama. This is interesting to me because most of the media reports about Democratic turn-out point to dissatisfied Obama supporters not turning out for their local Democrats. I can’t speak for all Democrats and the house party certainly isn’t a scientific sampling, but it was encouraging to see quite a few people turn out for Miller, despite possibly being disappointed in Obama.
Personally, I think Obama has done a great job considering what he has going against him. Sure, I disagree with him from time to time (such as a lot of the bipartisan wishful thinking), but I’m not sure Obama would have accomplished what he had if he had taken that position, so I give him a pass. I guess I’m just an O-Bot, but I don’t blame him for not getting my ponies and rainbows. I blame the obstructionist Confederate Party of Big Business (aka Republican Party). I think we need to channel our fear and anger away from minor intraparty mistakes and quibbles and channel it against the political party that is holding up all true progress for the American people.
If you are a liberal and are feeling unmotivated to vote, just think about what it would be like to have a tea partier as your representative. That is what is at stake. Do you want government to work for you or against you? There is no other choice.
Despite the overall outlook and common beltway wisdom, I’m feeling encouraged and can’t wait to vote for Brad Miller and Elaine Marshall.
There's a lot of documentation out there on how to mount ISOs in Microsoft System Center Virtual Machine Manager for Hyper-V hosts. It basically involves setting up permissions on the library shares so that the Hyper-V host machines can consume the share, then setting up constrained delegation in Active Directory. Here's a link: http://blogs.technet.com/b/dutchpts/archive/2009/02/09/hyper-v-and-scvmm-2008-mounting-iso-s-from-a-network-share.aspx?wa=wsignin1.0
And here's the error…
VMM cannot complete the Hyper-V operation on the HVSERVER1.domain.com server because of the error: 'NewServerHost' failed to add device 'Microsoft Virtual CD/DVD Disk'. (Virtual machine ID 119730D6-8939-4CB9-8456-7941F6925279)
'XSIntWeb1-V': The Machine Account 'XSINC\HVSERVER1$' does not have read access to file share '\\HVSERVER1.domain.com\ISOs\en_windows_server_2008_r2_standard_enterprise_datacenter_web_x64_dvd_x15-50365.iso'. Please add this computer account to the security group of file share. Error: 'General access denied error' (0x80070005). (Virtual machine ID 119230D6-7929-4EB9-9456-6946F6925279)
(Unknown error (0x8001))
Resolve the issue in Hyper-V and then try the operation again.
If you follow those steps exactly and still have issues, then there might be one more gotcha. Are you trying to connect to a VMM library that is hosted on the same server as both the VMM server and the Hyper-V host's parent partition? (Yes, this is a supported configuration.)
If so, you need to add the NT AUTHORITY\Network Service user account to the share and NTFS permissions. The reason is that the CIFS (SMB) file share is local to the computer needing access. As such, instead of the user appearing as the Hyper-V parent server machine name (such as HVSERVER1$), it will appear as the local account that the Hyper-V server is running as, which is typically the built-in Network Service account.
What makes this a 'gotcha' is that the error message explicitly states the machine account as the culprit. I only figured this out through the power of Process Monitor by SysInternals, which clearly showed the ACCESS DENIED is occurring when Network Service hits the share.
A very brief tech mystery today!
We have not upgraded to Exchange 2010 yet at work and are still on Exchange 2003 (yes, 2003). That upgrade is scheduled for a little later this year, but until then, I have to continue to support 2003.
I ran into a strange mail flow issue today that ends up being the result of a combination of Exchange 2003 and Outlook 2007 or newer. One of my users was trying to send an update to a meeting request, but recipients outside of our domain (external SMTP recipients) were getting stuck in the queue. The additional information in the queue just said "Unable to open the message for delivery." That clued me in that it wasn't an external SMTP rejection of the message (invalid email address or whatever). So I did some googling.
It turns out there's actually a known issue for Outlook 2007 or Outlook 2010 (or newer) clients sending meeting updates via Exchange 2003. It must not happen all the time, because we've had Outlook 2007 deployed for years and never saw this issue before. In fact, it didn't start happening until a user on Outlook 2010 sent a meeting update. Maybe it's just coincidence – I'm not really sure.
Anyway, here's the KB with all the details. The article isn't clear, but to double check if you have this error by enabling diagnostic logging, you need to set MSExchangeTransport\Exchange Store Driver to Maximum. Once you do that, go back to the queue, select the outbound server the stuck message is sitting in, right click and select "Force Connection." Then you can look in the event viewer for the specific error to confirm this is your issue.
Don't forget to set the registry entry after applying the hotfix!
As has been mentioned in plenty of blogs before, Windows Phone 7 will not support a the traditional experience of multitasking applications. With the exception of certain bare Windows CE devices, multitasking in PDAs and Phones has never really been like the desktop experience and that's okay. I don't expect it to act the same. Basically, the normal multitasking paradigm on these devices is that the app is sent to the background and another app comes to the foreground. It works really well in Windows Phone Classic (aka Windows Mobile) and Android. The Apple iPhone takes a different approach. Each app must save its state and exit when it is 'sent to the background' except the approved built-in Apple apps. Windows Phone 7 copies this approach, because apparently emulating Apple is the way to win a market (this has worked wonders for Zune, apparently).
To be fair, the WP7 approach is a bit more flexible. First, apps aren't necessarily closed when put in the background, but they are paused. Second, apps can request permission from Microsoft to be allowed to continue to operate in the background if they need to. That actually could be a decent model, as not all apps need to continue to run in the background, but this all hinges on Microsoft allowing you to run in the background if you need to. That's not a good place to be when you are trying to get investors to believe in your new cutting edge piece of software for this new device. By a single Microsoft employee's whim alone, your entire app could be neutered. Great.
I multitask like a crazy fool on my wonderful HTC Touch Pro 2. I usually have about five or six things open. I also write a lot of software. This may come as a shock to some, but in your standard Windows app, if you receive no input, your app does nothing – literally nothing! This is because Windows apps are message-based. Your app will block while waiting for a message (0% CPU). Okay? It won't do anything. Nothing! If you are in the background, you receive no input. So unless you have a timer or another unblocked thread, your app is effectively paused. Plus, even if it has a timer or thread, unless you are using it to refresh a UI element, it's probably doing something you think is important. Finally, if your phone goes to sleep on Windows Mobile, unless you specifically execute a set of functions to keep the device's idle timer awake, your app, along with the entire device, will sleep, timers and all. So the "battery life" excuse is just that: an excuse! So what's the point of pausing? The only "good" purpose is to offer some sort of control over misbehaving applications. That's a fine gesture. But, as a power user, how about giving me the control to whitelist apps that I want to be in the background? Oh, I can't because Charlie Kindel knows what's best for us. (Queue the halos and angelic chorus.)
So anyway, I've been reading the WP7 apologist posts on various Microsoft forums. There are a hell of a lot of people who are okay with WP7 not offering a true multitasking experience. That's fine. Not everybody computes the same. Some people run all their desktop apps in full screen, can't stand a second monitor, and hide their task bar. It feels like trying to compute with two broken wrists to me, but hey, I won't begrudge them. They had their own choice to use their computer that way. What is pissing me off are the number of people who claim This Way Is The One True Way and those of us that want to multitask, really don't need it and won't miss it! Oh hell to the no! I will definitely miss it. You want to know how? Because I'm not completely stupid and I know my computing habits.
As if being forced to have the ugly blue-box "metro" theme be the only home screen available on WP7 wasn't torture enough!
So, to Mr. Kindel and Kindel brown-nosers: If you don't want to multitask on your phone, that's fine. I mean, really, more power to you! But can I, and other power users like me, please have this option that would require almost no effort on MS's part to implement? After all, CE has multitasking built-in. It takes more effort to stop it from multitasking than to keep it in. I'm okay with a supposed shorter battery life (snicker). I just want my control back. Windows CE is a really cool embedded operating system. Let's not neuter it with silly Apple-like rules, okay?
I was searching the Google for information on Windows Phone 7 regarding database support. There will be no database support. Interestingly, I found discussion with somebody venting about this (and the other, many, lacking features of Windows Phone 7) and saw an interesting reply from a Microsoft employee. Quoted in full (sic and all that apply)…
I'm part of the team that supports all Mobile and Phone technologies. Our team still remains obligated to continue supporting 6.5 and the corresponding Enterprise Business market.
Clearly the target market for Windows Phone 7 is the consumer and its entire architecture has been designed from scratch by the best architects at Microsoft, who left other divisions within the company and converged to brainstorm the specific needs of the consumer, as contrasted with businesses (although there definitely is overlap).
Note that Marketplace for Windows 7 is set up in a way that any app posted there can be downloaded by anybody; it isnt intended for the needs of the Business who wish to deploy an app on the phone that only they are privileged to access.
The needs of the Enterprise Business customers will not go away and their needs must be, and will be, addressed differently.
For the moment, the limelight is on the Windows Phone 7 Series, but you will see Enterprise progress and Microsoft's continued support for phones used in business.
Mark Chamberlain Sr. Escalation Engineer | Microsoft Developer Support | Windows Phone 7
First, regarding the "best architects" wank wank stuff. You could have fooled me! Metro UI was interesting for about a day. Now it's just ugly to me. But I'll give it another shake once it's out of beta. It's not fair to bash on it too hard while it's still in beta. On the other hand, Mobile Shell 3 and SenseUI are still interesting and I've used both for a while now!
So, according to Mr. Chamberlain, the enterprise customers needs must and will be address differently? Differently? As in, not using the draconian Windows Phone 7 model? Do I dare hope for life of Windows Phone 6.5 beyond 6.5.3? Do I dare hope for Windows Phone 6.5 to be renamed Windows Phone Enterprise Edition with a new wicked CE7 kernel and updated Compact Framework 4.0 (with Silverlight)? Do I dare hope for Visual Studio 2010 (and beyond) support?
Do I dare hope for life on the mobile operating system that could easily be modernized and that I've enjoyed using and programming for over the last ten years?
A side note: T-Mobile can't keep the HD2 in stock! All that on an "outdated" OS. I could have told you that putting a decent CPU in a HTC SenseUI (aka TouchFlo 3D) powered device would do that. But nobody listens to me… :-)
John McCain said on a radio interview that the GOP won't cooperate for the rest of the year. I know, I know. Eleventy billion people are going to say this in unison, but I just can't NOT post this!
All together now... Since when has the GOP cooperated with the Democratic majority in the past two years?
I have always been a huge fan of Windows Mobile. It is (was?) literally a computer in my pocket. A barrage of less-than-spectacular devices combined with long periods between (small) updates left the platform behind its newer competitors -- the iPhone and Android. Now, I won't get into a deep discussion of what happened in the past, but let's just say that thanks to the efforts of HTC, Windows Mobile/Phone stayed fairly competitive, all things considered.
Now Microsoft has introduced Windows Phone 7 Series. They want to get back into the game big time. What initially looked so freaking awesome has turned out to be Microsoft's version of the iPhone -- a heavily locked down device with a supposed "focus on consumers." Apparently a focus on consumers means telling consumers how they are supposed to enjoy their devices and maybe cutting them a break and giving them some third party apps that absolutely cannot run in the background. That's the straw that broke the camel's back for me. As a developer and power user, I can't buy a Windows Phone 7 Series device if I can't tweak the hell out of it like I can my current device, a HTC Touch Pro 2, running Windows Phone 6.5.
So, what few Windows Mobile fanboys still exist out there, read the following article and cry at the end of an era. And also plan your next Android purchase. God, I hate Java. But what can I do? Microsoft has left me with no choice.
So supposedly in the future multitasking will be available when they figure out how not to impact the user experience (wtf? never heard of a priority queue? mutltitasking is not rocket science). If and when they do, I might be back on board. Until then, with no unmanaged code, no memory cards, no multitasking, and a load of other "nos" where Microsoft forces us to use our devices their way and not ours, I'm not buying a Windows Phone 7 Series device. Very sad considering how cool it looks. I mean Silverlight UI and XNA games? Hell to the yea! But it's no longer a minicomputer. It's just a Zune with a phone. I'm not interested.
So, I hope their commitment to the 6.5 platform is not lip service, because I'm relying on that while I watch to see what happens with Windows Phone 7 Series. I'm hoping that by "7.1" it will still look smooth as silk, like it does now, but will be back to being a mini-computer, like its in-spirit predecessors.
Eureka Seven: Good Night, Sleep Tight, Young Lovers is a fast-paced action-packed love story. It has a very different plot from the original Eureka Seven series, so don't expect a sequel!
That said, the plot does parallel the series in several ways. The basic premise of aliens attacking the Earth and humans fighting back remains. Where the series portrayed the aliens as basically misunderstood and unintentionally damaging, the movie portrays them as more generically malicious, even though they did shoehorn some more 'innocent misguided intentions' stuff later in the plot.
Eureka has changed a lot. She's more of a fusion of Eureka and Anenome in the series, including frequently yelling "idiot" at Renton. That took a lot of getting used to for me. Interestingly, Novak and Anenome basically replaced Norb and Sakuya's roles in the story. It will raise a few eyebrows at first, but it worked.
For the first 45 minutes, I was a bit disappointed. Character development seemed forced (probably due to trying to fit a series worth of plot into a two hour movie). However, it won me over at the point when Holland was explaining the Gekko crews' motives to Renton. This was one of my favorite moments because it actually gave a nod to the series! I'm not going to give it away, but it was really cool how they did it. After that, the story seemed much less rushed. It was still confusing at times, but a few characters were also confused by what was happening. So I figure confusion was intentional.
Trapar waves were completely unexplained in the film. So there is no clue what it is or how it works in this universe, but vehicles do use it for lifting, so it's there. Eureka has a sensitivity to light, but that is also never explained. You'll find "unexplained" being a bit of a recurring theme. lol.
And the ending, ahh the ending! It was truly unique to the movie and it worked! Just like the series, it showed love, sacrifice, maturity, and made up for the more confusing parts.
I love the original series. It is actually not just my favorite Anime, but my favorite story in any form. I love it! On a scale of zero to five, I give it 5/5 easy! However, I can't rate the movie that high. Don't get me wrong, it was a great story. I would give it a solid 4/5 star rating. If you liked the series, you will like the movie, even if just to get a little more of a Eureka and Renton fix. If you are not familiar with the series, you will still like it, but be prepared for a confusing ride.
And now some random notes:
- They actually give a reason for the "seven" this time!
- Very few references to the electronica scene this time (disappointing).
- Moon Doggie can apparently be in a KLF the Gekko at the same time! Plot holes resulting from reused animation cells can be funny. ;-)
- Baby archetypes can say one word and they tend to say it in an incredibly annoying voice.
- The final version of Nirvash in the movie kicks even more butt than in the series.
- The literal translation of the Japanese subtitle is "Pocket Full of Rainbows." I'm not really sure why they changed it to "Good Night, Sleep Tight, Young Lovers" as there were ample references to rainbows throughout the series. Sometimes subtitles are changed because something is lost in translation. Here, I don't know.
Anyway, I really hope Bones returns some day to the original series' universe. I still long for more!! :-)
There is basically no information on Teh Googlez (or Teh Bing!) on this error, so I hope this helps somebody out there.
I was trying to install Microsoft Dynamics CRM 4.0 in our beta environment, which is in its own forest. Every time I installed it, no matter what settings or tricks I tried, I would get the following error:
For the search engines and those who can't read text in pictures, it says…
Action Microsoft.Crm.Setup.Server.AddIncomingServerToPrivUserGroup Action failed. There is no such object on the server.
If you click Retry, it won't work. If you click Ignore, you get a few more errors and then the installation fails at the end. If you click Abort, you save yourself some time and it just quits right there. At this point you may have to manually undo parts of the CRM installation. Start with running the uninstaller, of course. Then check to make sure the CRM databases are deleted off your SQL server and the Active Directory objects got deleted as well.
At this point, I looked at the logs to see if I could gleam what happened. Unfortunately, the logs did not provide any more help as they just repeating what was in the error box above. Here's a snip.
18:07:17| Error| Install exception.System.Exception: Action Microsoft.Crm.Setup.Server.AddIncomingServerToPrivUserGroupAction failed. ---> System.DirectoryServices.DirectoryServicesCOMException (0x80072030): There is no such object on the server.
at Microsoft.Crm.Setup.Server.Utility.ADUtility.AddAccountToGroup(String accountName, DirectoryEntry groupEntry)
at Microsoft.Crm.Setup.Server.AddIncomingServerToPrivUserGroupAction.Do(IDictionary parameters)
at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo)
--- End of inner exception stack trace ---
at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo)
at Microsoft.Crm.Setup.Common.Installer.Install(IDictionary stateSaver)
at Microsoft.Crm.Setup.Common.ComposedInstaller.InternalInstall(IDictionary stateSaver)
at Microsoft.Crm.Setup.Common.ComposedInstaller.Install(IDictionary stateSaver)
at Microsoft.Crm.Setup.Server.ServerSetup.Install(IDictionary data)
18:07:17| Info| Microsoft Dynamics CRM Server install Failed.
18:07:17| Info| Microsoft Dynamics CRM Server Setup did not complete successfully.
Action Microsoft.Crm.Setup.Server.AddIncomingServerToPrivUserGroupAction failed.
There is no such object on the server.
15:40:56| Info| === Setup bootstrap logging started 1/27/2010 3:40:56 PM ===
15:40:56| Info| Bootstrap version: 4.0.7333.3.
15:40:56| Info| User: Administrator.
15:40:56| Info| Managed Setup exited with code -2.
15:40:56| Info| === Setup bootstrap logging ended 1/27/2010 3:40:56 PM ===
It turns out that the problem is the fact that my Exchange server is in another forest. This is mentioned essentially nowhere that I can find, but a call to Microsoft Support pinned the issue down. The two domains in the two forests have a two-way trust, but the installer is still not happy.
So what do you do?
Well, it's not that bad. First, run the installer, but do not put in a mail server when it asks. Ignore the email server warning and proceed anyway. The installation will succeed this time. Huzzah! Now, we need to add in the Exchange server manually. Go to the CRM OU you created in Active Directory, open the properties of the PrivUsergGroup and manually drop in the Exchange server computer object (from whatever domain you want) to the list of members. Done!
Some extra notes…
Make sure you are installing as a local forest domain admin. If you install using an admin from another forest, you may get this error:
Similar to the previous error, this occurs because the installer can't seem to cross forest boundaries when populating the PrivUserGroup group. For the search engines and those who can't read text in pictures, it says…
Action Microsoft.Crm.Setup.Server.AddCurrentUserToPrivUserGroup Action failed. There is no such object on the server.
The solution is to use a local forest domain admin (one contained in the same forest as the CRM installation) for running the CRM installer.
Yet another modern sloppy Microsoft installer with an overly verbose log that tells you abso-fricking-lutely nothing useful about the installation error! Ever since about SQL Server 2005, the installers for MS products have become less and less reliable – even on virgin servers! The worst I've encountered so far is TFS 2005 (server side, that is – client side is a breeze). SQL 2008 is a very close second. Hopefully Microsoft will start making better installers soon. (Or, at they very least, not requiring end users to burn a support case on an installer issue.)
So is Cincinnati really overrated or is the SEC just that damn good? The Gators destroyed the Bearcats tonight in the Sugar Bowl. I'm a Gator fan so I'm happy! I did not understand the BCS rating the Gators #5 after losing to Alabama in the SEC championship. And tonight I was vindicated. The Gators should have been the #3 team in the polls. Just because you are undefeated does not mean you are that good.
Not that it matters much because the net result would have been the same (Sugar Bowl invitation). It's just another example of how the Bowl system is broken and we need a playoff system in I-A college football! If we had a playoff system, I bet you anything it would have been an Alabama / Florida rematch.
And finally, I have to give a big thumbs down to the Fox game commentators. There was about a total of 12 minutes where they actually called the game. The rest of the time they spent talking about football inside drama and politics. They spent about an entire quarter talking about whether or not Tim Tebow will be any good in the NFL (my prediction: he will become a dominant QB after a few years when he finally gets a chance). It was the worst called bowl game I've ever watched!
But no matter. The Gators won 51-24.