Showing posts with label Vista. Show all posts
Showing posts with label Vista. Show all posts

Thursday, February 12, 2009

How to Synch Google Calendar with a SmartPhone Running Windows Mobile without a Computer.!

Finally.!

image

I just discover that Google has a setup that supports the Microsoft Exchange ActiveSync protocol to provide synch between their products and your Windows powered device. Follow the instructions in Set Up Your Windows Mobile Phone.

I did this configuration without having to craddle my SmartPhone to the computer.  I have the Motorola Q9c running Windows Mobile 6.1.  On your phone, open up  ActiveSync.

image

select Menu

image

select Add Server Resource.  After this step. I followed the instructions on their site. [I repeated them here for posterity]

image

add your username and password, leaving the domain field blank

image

Now on the next screen, I selected the Calendar option ONLY.

image

It was giving me some errors when I selected tasks, email, and contacts.  I think it does not handle tasks created in Outlook.

Click on Finish and Voila.!  It synchs wirelessly.!

image

Once it had synch all of my calendar entries, I went back and added the option to synch my Contacts.  The one drawback to synching your contacts for the first time, is that you have to go to Gmail and categorized them all.  And this is not fun when you have too many contacts…

image

This is very cool.  I have a share calendar with my wife and now we both can add/delete/modify entries into it, and it is REAL TIME synch.

Thursday, October 02, 2008

DocTools not working

For one of the projects we are working on, we need to make sure our end user documentation matches correctly the template provided by the customer. I have started playing with one of the products that the Patterns and Practices at Microsoft is using to generate their documentation. Take a look at their package: http://www.codeplex.com/doctools

After going through all of the installation and pre-requisites.  I was ready to try the sample Word Document they provide.  Snag.!  

First thing I notice is that the sample scripts are looking for the Microsoft DocTools in the c:\program files\Microsoft DocTools.  Changing those scripts brought to my attention that the install program gives you the ability to specify the path on where to install the DocTools.  However, it will always install to the (x86) directory on my Vista x64.

The main error I was getting was:

PS C:\DocToolsDemo> .\HTML.cmd

C:\DocToolsDemo>PowerShell ConvertToHTML.ps1 ESBIntro.docx .\outputHTML """C:\Program Files (x86)\Microsoft DocTools\Document Converter\Formatting\MSDN2\xsl""" convertESBConfig.xml

    Directory: Microsoft.PowerShell.Core\FileSystem::C:\DocToolsDemo

Mode                LastWriteTime     Length Name
----                -------------     ------ ----
d----         10/1/2008   9:10 AM            outputHTML

    Directory: Microsoft.PowerShell.Core\FileSystem::C:\DocToolsDemo\outputHTML

Mode                LastWriteTime     Length Name
----                -------------     ------ ----
d----         10/1/2008   9:10 AM            html
Add-PSSnapin : No Windows PowerShell Snap-ins are available for version 1.
At C:\Program Files (x86)\Microsoft DocTools\Document Converter\ConverterLibrary.ps1:9 char:15
+         Add-PSSnapIn  <<<< ppConverter.Cmdlets

--Splitting: C:\DocToolsDemo\ESBIntro.docx
An Error Ocurred: The term 'Split-Document' is not recognized as a cmdlet,
function, operable program, or script file.Verify the term and try again.

PS C:\DocToolsDemo>

After doing all of the regular stuff (check PATH, re-install, start/stop program, google), I could not get this error to go away.

The problem seems to be with the OS I am running.  Since I am running a 64bit OS, I need to call the PowerShell that is on the c:\windows\syswow64 and not the one in the regular 32bit.  This is accomplish by running the one marked with the (x86)

image

Once I opened this one, ran the set-executionpolicy remotesigned command.  It ran and split the Word document successfully and generated my HTML help compile file.

image

One of those simple bugs that can waste a whole hour for you.!

Thursday, April 03, 2008

Blue Screen on Vista SP1

Do blue screen still exists in the new and latest Operating system from Microsoft... ?

image 

[Main Instruction]
Windows has recovered from an unexpected shutdown

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.0.6001.2.1.0.256.4
  Locale ID:    1033

Additional information about the problem:
  BCCode:    a
  BCP1:    0000000000000000
  BCP2:    000000000000000C
  BCP3:    0000000000000001
  BCP4:    FFFFF800026742D4
  OS Version:    6_0_6001
  Service Pack:    1_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini040208-01.dmp
  c:\temp\WER-374105-0.sysdata.xml
  c:\temp\WER6B5F.tmp.version.txt

Clicking on the Check for Solution button, it deleted those files and close the dialog box really quick.  So I went and check on the Windows Error Reporting folder located at C:\ProgramData\Microsoft\Windows\WER\ReportArchive

In there I found two files:  Report.cab and Report.wer.  Opening the Report.cab yield those 3 files reported on the Dialog box.

image

Now I went and open the version.txt file:

Windows NT  Version 6.0 Build: 6001 Service Pack 1
Product (0x4): Windows Vista (TM) Enterprise
Edition: Enterprise
BuildString: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Flavor: Multiprocessor Free
Architecture: X64
LCID: 1033

The sysdata.xml contains a list of all of the drivers currently loaded:

image

so right now I don't know what caused the blue screen, and I am not sure if this information was ever transmitted to Microsoft.  For the record I have a Dell D820 with 4GB Ram running Vista Enterprise 64bits.

I have started to see more and more people getting blue screen's on Vista after they installed SP1. Coincidence?  ;)

Wednesday, February 13, 2008

WSS 3.0 studio extensions not working on x64 Vista

One more of those little annoyances. I can't play with this new set of tools on my laptop: Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions, Version 1.1, because it does not support 64bit.

image

bummer. Time to fire off my Windows 2003 Virtual machine.. :(

Wednesday, November 21, 2007

How to edit rich text in SharePoint 2007 forms

Since I have been using Window Live Writer, I have not had the need to write all of that html code (what is HTML?). I edit using Live Writer, and then I switch to HTML view, copy and paste the formatted text into the SharePoint text box. I thought it was weird that Microsoft will only give a blank text box and you need to go and figure out all of the markup tags.



Then I saw on this other developer screen that his text boxes look a lot different from mine..!!



Clicking on the
Click for help about adding HTML formatting.
just take you to the normal help, nothing useful there.

Well, I found out that it was just another x64 vs x32 bit kind of deal. Since moving to the 64bit bandwagon, I almost exclusively use Internet Explorer (64 bit). It is a great way to get to the Microsoft sites without being bogged down by all of the flash advertisement (oh yeah, those flash do not work on 64bit... ;)

However, there is a whole new world out there if you use the 32bit version of Internet Explorer.!!

yikes.

Tuesday, November 13, 2007

Biztalk 2006 R2 Upgrade gotchas?

I just finished upgrading to R2 on my Vista x64. So far everything seems to be running fine, except....

Business Rules Engine:

There is a new location for the assemblies now. On Biztalk 2006, the location for the BRE assemblies was this

c:\Program Files (x86)\Microsoft BizTalk Server 2006\Microsoft.RuleEngine.dll

However, after removing my 2006 version, and freshly installed the R2 version, I have to go and recompile all of my assemblies that had a reference to the Microsoft.RuleEngine. The new location is

C:\Program Files (x86)\Common Files\Microsoft BizTalk\Microsoft.RuleEngine.dll

Other than this, everything seems to be running smoothly (Orchestrations, pipelines, etc...) so far. I will update this post as I find any more gotchas (if any... ;)

Friday, July 13, 2007

SWIFT Accelerator v.2.3 not working on Vista - Part 2

I guess that there was a reason I attended the Technical Training on the SWIFT Accelerator for Biztalk. Technically speaking, the SWIFT Accelerator does not work under Vista, because it requires WSS (Windows Sharepoint Services) 2.0 with SP-2.



However, in my rush to try to view how the accelerator work, I downloaded the Message Pack and not the Accelerator installation. The accelerator is a separate component that you must pay for (it is licensed on a per CPU basis).

The Message Pack are just updates to the Schemas and Infopath forms that are version specific. Microsoft release these updates to go alongside the new versions from SWIFT.

Getting trained by the SWIFT guys themselves was very informative.! From their perspective, their organization has not have the level of success that they have in other countries of the world. I believe that they mentioned something in the neighborhood of over 200+ countries associated with the SWIFT.

If you want to get familiar with the SWIFT and its Accelerator in Biztalk 2006, check out these 2 webcast on the MSDN:
  1. Using the Biztalk Accelerator for SWIFT (Level 200) - (30minutes)
  2. Inside the BizTalk Accelerator for SWIFT (Level 300) - (1.5hrs)
Something I got from the training is that Microsoft has invested quite a lot of effort and time getting this accelerator working the way it is. It is quite amazing at all of the functionality you get right out of the box after you installed it. All of the BRE and the Infopath forms are just great.

Once you install the SWIFT Accelerator in Vista, you get all of the messages, samples, and documentation. However, you won't get MRSR InfoPath forms. Also, you wont get the Message Repair and Reconciliation modules.

Just as an FYI, these are the SWIFT messages you will get when installing the Accelerator:
  • GPA and FIN System Messages
  • Customer Payments Cheques
  • Financial Institutions Transfers
  • Money Market Derivatives
  • Collection Cash Letters
  • Security Markets
  • Treasury Markets
  • Document Credits Guarantees
  • Travelers Cheques
  • Cash Management Customer Status.
There is tons of information on the SDK. I specifically like how they put the BRE inside the pipelines so that they can apply Rules to both incoming/outgoing messages.



I hope in the future I will have an opportunity to work with this Accelerator. It seems so robust and fits perfectly to solve the problem at hand.

Tuesday, July 10, 2007

SWIFT Accelerator v.2.3 not working on Vista




This week I am taking a SWIFT (Society for the Worldwide Interbank Financial Telecommunication) training course sponsored by the Microsoft Virtual TS program. I am trying to install the BizTalk Accelerator for SWIFT 2006 v2.3 Message Pack on my Vista machine.

Trying to install this latest version does not work, I get this message:
Platform Prerequisites Missing
Based on the components you've selected to install, you must first install the following platform prerequisites. Please cancel this installation, install the prerequisites, and rerun the Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack Installation Wizard to continue.

- BizTalk Accelerator for SWIFT 2.3 + Service Pack 1
So I proceeded to download the BizTalk Accelerator for SWIFT v2.3 Service Pack 1. Running the setup, give me this other error:
Microsoft Biztalk Accelerator for SWIFT 2.3 Rollup not found or this package does not contain compatible patch.
Digging a little deeper into this error, I found out this on the log entry:
[6:38:02 AM Info] Product code: {2CBEA167-9DDA-48D7-8F15-467082C3DE8D}
[6:38:02 AM Info] Product name: Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack
[6:38:02 AM Info] Product PIDSKU: Q15-00180
[6:38:02 AM Info] Product Code (MPC): 76835
[6:38:02 AM Info] OEMID:
[6:38:02 AM Info] Product is not already installed.
[6:38:02 AM Info] Successfully opened Msi package: C:\Downloads\Biztalk\SWIFt\A4SWIFT2006MessagePack2-3\A4SWIFT2006MessagePack2-3\Msi\Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack.MSI
[6:38:02 AM Info] Raw module path: c:\temp\EBZ40425.tmp\Setup.exe
[6:38:02 AM Info] Universal module path: c:\temp\EBZ40425.tmp\Setup.exe
[6:38:38 AM Info] Detecting platform component: Setup runtime files
[6:38:38 AM Info] The minimum required version is: 2.1
[6:38:38 AM Info] The currently installed version is: 0.0
[6:38:38 AM Info] Component is not installed.
[6:38:38 AM Info] Detecting platform component: BizTalk Server 2004 Service Pack 1
[6:38:38 AM Info] The minimum required version is: 3.0.6070.0
[6:38:38 AM Info] The currently installed version is: 3.5.1602.0
[6:38:38 AM Info] Component already installed.
[6:38:38 AM Info] Detecting platform component: BizTalk Accelerator for SWIFT 2.3 + Service Pack 1
[6:38:38 AM Info] Component is not installed.
[6:38:38 AM Info] Required platform components: BizTalk Accelerator for SWIFT 2.3 + Service Pack 1
[6:39:36 AM Info] User cancelled setup.
Humm... Does it means I have to have the BizTalk Accelerator for SWIFT v2.1 2006 Message Pack before installing the v.2.3? I try installing the SWIFT Accelerator v.2.1, and this is what I get:
Platform Prerequisites Missing

Based on the components you've selected to install, you must first install the following platform prerequisites. Please cancel this installation, install the prerequisites, and rerun the Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack Installation Wizard to continue.

- BizTalk Accelerator for SWIFT 2.1 + Service Pack 1
Now, this is getting complicated. Looking at the log file I find the same message as before:
[6:48:17 AM Info] Product code: {2CBEA167-9DDA-48D7-8F15-467082C3DE8D}
[6:48:17 AM Info] Product name: Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack
[6:48:17 AM Info] Product PIDSKU: Q15-00180
[6:48:17 AM Info] Product Code (MPC): 76835
[6:48:17 AM Info] OEMID:
[6:48:17 AM Info] Product is not already installed.
[6:48:17 AM Info] Successfully opened Msi package: C:\Downloads\Biztalk\SWIFt\A4SWIFT2006MessagePack2-1\A4SWIFT2006MessagePack2-1\Msi\Microsoft BizTalk Accelerator for SWIFT 2006 Message Pack.MSI
[6:48:17 AM Info] Raw module path: c:\temp\EBZ42439.tmp\Setup.exe
[6:48:17 AM Info] Universal module path: c:\temp\EBZ42439.tmp\Setup.exe
[6:48:31 AM Info] Detecting platform component: Setup runtime files
[6:48:31 AM Info] The minimum required version is: 2.1
[6:48:31 AM Info] The currently installed version is: 0.0
[6:48:31 AM Info] Component is not installed.
[6:48:31 AM Info] Detecting platform component: BizTalk Server 2004 Service Pack 1
[6:48:31 AM Info] The minimum required version is: 3.0.6070.0
[6:48:31 AM Info] The currently installed version is: 3.5.1602.0
[6:48:31 AM Info] Component already installed.
[6:48:31 AM Info] Detecting platform component: BizTalk Accelerator for SWIFT 2.1 + Service Pack 1
[6:48:31 AM Info] Component is not installed.
[6:48:31 AM Info] Required platform components: BizTalk Accelerator for SWIFT 2.1 + Service Pack 1
[6:49:10 AM Info] User cancelled setup.

Nice. Circular references.!!. So apparently it wont install on my Vista machine. There is some hard coded dependency that wont allow this installation to continue. It looks like it is a setup dependency and not a BizTalk dependency.

I guess I have to get back to using my Windows 2003 Virtual PC...

Thursday, June 14, 2007

Outlook 2007 is not responding in Vista

Yesterday, my windows update pick up a lot of updates to be performed to my Vista machine. Being the good MS citizen, I say yes, go ahead. After the reboot (of course there is a reboot.!) my Outlook 2007 keep freezing up on me.



Looking through all of the updates, I've found that one of the updates was the
http://support.microsoft.com/kb/933493, which tries to fix some of the performance issues in outlook 2007.

This update is related to this other KB article: http://support.microsoft.com/kb/932086/ that states that the size of the PST file might affect performance... hummm...



My outlook.pst file is 131MB. Googling around found a couple of post that directed me to rename some files from the upgrade/import from Outlook 2003 to 2007.

Shut down Outlook 2007, then I renamed the following files:
"C:\Users\awing\AppData\Local\Microsoft\Outlook\extend.dat" [to extend.old]
"C:\Users\awing\AppData\Local\Microsoft\FORMS\FRMCACHE.dat" [to frmCache.old]
Open Outlook 2007 back, and now it seems to be working fine again. I have not experienced any more Not Responding hang ups.

oh well.

Tuesday, May 08, 2007

Vista and Dual Monitors

Ever since Vista Beta 1, I have been dealing with the dual monitor problem. However, once I got a new Dell laptop (D820) with the NVidia Quadro NVS 110M video card, little annoyance became a NUISANCE. Running Vista on a laptop, Vista always insist that the external monitor that you connect, HAS to be my primary monitor..!!

Every time I connect a new monitor, Vista goes and make it my primary monitor, and then I have to manually configure it every time to use the laptop monitor as my Primary. Things gets worse if you have a docking station. On my dual monitor setup I am used to keep my task bar on the right side and keep the left monitor as an extended area.

Issue with this is that every time a screen refresh happens, it seems to forget its configuration. By screen refresh I mean: Screen Saver comes up, you locked your workstation, you undock the laptop, etc, etc. I see it working fine and in about 10 seconds it flickers, and set the monitor to 1-2 instead of 2-1.

This is my saved lineup:


after I come back from a screen saver, or a locked state, this is what Vista sets it to be:


For a while, I thought on becoming left handed, so this will not affect me. Eventually, I got so used to start the nVidia Control pannel and fixing this all of the time, that I've got used to.

After hearing so many people complaining on this issue and no-one finding a good solution, I took it to find the source of this annoyance.!

Enter TMM. Transient Multimon Manager. This is a feature of Windows Vista that is designed specifically for mobile users (laptops, etc..). What this feature does, is that it keeps track any changes to your display settings and try to provide a best experience possible. Right...;)

The TMM runs as a scheduled task. In Vista, bring up the Task Scheduler, and under the Windows tasks, you will see the TMM entry:

UPDATE [5/12/07]: It is by default under the MobilePC hive. I have deleted the TMM entry and then imported, so my snapshot is wrong. [thanks Jim for pointing that out.. :D]



You can right click on it and select to either Disable it or Delete it.

After you disabled or deleted, then click on the actions panel and click on the Display All Running Tasks link to see if it still running.


If so, then select it and click on the End Task button.


That's it.!! This shuffling of monitors will never happen again.

Notes: The only downside to deleting the TMM task, is that if you have dual monitors, and you have some programs that are displaying on the secondary monitor. If you un-plug the external monitor, then Vista will NOT put those programs back into your main monitor. Which means that those programs are now displayed somewhere else that you can't see or access. A workaround this will be to manually put all of the programs back to the main monitor before un-docking your laptop.

Other than that, I can see no other negative impact on deleting the TMM task. If you prefer, you can export the TMM task and save it to an xml file.

Thursday, May 03, 2007

BTW, ThumbPosition DOES HAPPENS..!!

So my life revolves around DebugView. I used it constantly when debugging Biztalk or Web Services. It is a great tool to have.

Then one afternoon, I am running MOSS on a VirtualPC 2007 (64bit) of course, and doing some weird calls from Vista into my VPC, when out of the blue, I see this message showing up on my debugview console:

MSEnv extensibility IClassFactory::LockServer(TRUE), lock count: 1 MSEnv extensibility IClassFactory::LockServer(TRUE), lock count: 2 MSEnv extensibility IClassFactory::LockServer(TRUE), lock count: 3 MSEnv extensibility IClassFactory::LockServer(FALSE), lock count: 2 MSEnv extensibility IClassFactory::LockServer(FALSE), lock count: 1 %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s ThumbPosition got called! That never happens. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s


That's very strange, or should I say WTF?... A search on Live.Com give me a link to the scroll event types, ScrollEventType Enumeration.

I wonder which developer wrote this assert.!!

Anyways, my environment is Vista Enterprise 64bits, VStudio Team Suite with SP1, MOSS 2007, in case someone finds the same error.

It's a conspiracy man..:S

Tuesday, May 01, 2007

Reading appSettings from BTSNTsvc.exe.config in Vista


I am not getting into all of the discussions on what's the best way to store and retrieve information at run time when running Biztalk 2006. For small things, I like to use the BTSNTsvc.exe.config file.

For Windows 2003 you will open the file and add the keys you need, i.e:
<appSettings>

<add key="xxx.newYear" value="2009"/>

<add key="xxx.newXSN" value="http://site.com/template.xsn"/>
</appSettings>
Then inside your orchestration you can have code like this inside your expression/message assignment shape:

sXSNPath = System.Configuration.ConfigurationSettings.AppSettings.Get("xxx.newXSN");
sYear = System.Configuration.ConfigurationSettings.AppSettings.Get("xxx.newYear");

and you can test the values by writting them out:

System.Diagnostics.Trace.WriteLine("bts- XSD:[" + sNewXSNPath + "]");
System.Diagnostics.Trace.WriteLine("bts- Year:[" + sYear + "]");


However, if you are running Vista, these calls return blanks.

The reason for this is the new feature of Vista called Virtual Stores. What this functionality is that it allows your running program to save information into one of the secured folders (Program Files). When in fact, it is creating a virtual location for you. In my case, the actual location of the BTSNTsvc.exe.config file that Biztalk is looking for is located at:

C:\Users\awing\AppData\Local\VirtualStore\Program Files (x86)\Microsoft Biztalk Server 2006

and not in the

C:\Program Files(x86)\Microsoft Biztalk Server 2006 folder.

This could get confusing for some users, since there is no errors or warnings about it. I can see how some applications could get out of sync really quick.

For instance if you have the UAC turn on, and have been using a software that stores its data on the c:\program files\Cust_App\. Then after a couple of weeks/months, you decide to turn off the UAC, you will find, that your application will have missing data.!



Thursday, March 29, 2007

SQL Server 2005 – SP2 available

We can *officially* run SQL Server 2005 on Vista... ;) All of those days of reading messages about SQL not being supported in Vista are finally over.!

Here is the query to determine your version of sql:

SELECT SERVERPROPERTY('ProductVersion')

9.00.1399

SQL Server 2005

9.00.2047

SQL 2005 with SP1

9.00.3042

SQL 2005 with SP2


You can download the SP2 at the SQL Server 2005 SP2 Download Page.

Wednesday, March 21, 2007

Cool Vista Secrets

I have found the site of Tim Sneath (Vista Technical Evangelist). He has posted a couple of hidden treasures that you can find on Vista. It is just AWESOME.

Here is the link:

http://blogs.msdn.com/tims/archive/tags/secret/default.aspx

My favorite secrets:
#4: Disabling UAC

#1: Open comand prompt

#2: Copy as path

#8: Zoom in Explorer.

#11: Deleting the Undeletable
nice, very nice... :)

Tuesday, March 20, 2007

Guidance Automation Toolkit Installation Failure on Vista

When trying to install the Guidance Automation Toolkit under Vista, you might encounter this error:
The installer has encounter an unexpected error installing this package. This may indicate a problem with this package. The error code is 2869.
This is an RTFM issue. ;) According to the documentation of December 2006, it mentions that this error is because of the UAC (User Account Control) of Vista. They also provide the work around: Run the MSI installer from a VStudio Command prompt that has elevated privileges (Run as Admin).

To install the Service Factory on Windows Vista

1. On the taskbar, click Start, point to All Programs, point to Microsoft Visual Studio 2005, and then click Visual Studio Tools.

2. Right-click Visual Studio 2005 Command Prompt, and then click Run as administrator.

3. Using the Change Directory (cd) command, navigate to the folder where the .msi file is located. For example: C:>cd users\me\downloads.

4. Run msiexec.exe using the following syntax.

msiexec /I "GuidanceAutomationToolkit.msi"

5. Complete the remainder of the installation as described in Installing the Service Factory.



the path to these set of instructions can be found on the CHM file:
Web Services Software Factory - December 2006
----Installing the Service Factory

--------How to: Install the Service Factory on Windows Vista

Thursday, February 22, 2007

Delete all RSS feeds from IE 7 on Vista

Annoying. If you need to delete all of the RSS feeds setup on your IE7, you will have to select each entry, right click, select delete, select OK. A quicker way is to go straight to the folder:

C:\Users\awing\AppData\Local\Microsoft\Feeds

and delete them from there.

Monday, February 12, 2007

Vista User Access Control (UAC)

When installing Vista for the first time, you will need to install a whole bunch of development tools. The easier way to install all of the dev tools, is to Turn off the UAC (User Access Control) temporarily, while installing all software. Then once you are done installing them, turn it back on.

This is how you access this feature:

Control Panel --> User Accounts --> User Accounts


Monday, January 22, 2007

Biztalk weird error in Vista

I was doing a simple training for this developer. Then I added a very simple webservice to be called from an orchestration. The first time I ran it, it worked fine. So I went and refactored it. By refactoring I meant deleting web service reference, re-adding it. Recreating new Configured Port on the ODX, etc. Then all of a sudden, I could not deploy this orchestration anymore.

It will compile correctly, but it will fail on the deployment with this error:

Error Error 6 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request.

Could not save the log to HTML file
"C:\Users\Arnulfo\AppData\Local\Temp\BT\PID4848\BizTalkAssembly\Update.log".

Exception: '',
hexadecimal value 0x1F, is an invalid character. '',
hexadecimal value 0x1F, is an invalid character.


Funny thing is that I did not have the BT\PID4848 directory. So I went and created it. Then I got this error:










I will dig this a little bit more. It is strange than by just shutting down the IDE, it does not fix the problem, but rather it gives a different PID number now.

I will update this blog when I find this culprit.

I have tried restarting the host from the IDE:

Wednesday, November 29, 2006

Office 2007 Hyperlinks not working in Vista RC-1

I get this error when I am trying to click on an Hyperlink on an office 2007 document running on Vista RC1:

This operation has been cancelled due to restrictions in effect on this computer. Please contact your system administrator.





Found a knowledge base article, that explains the error, but I have not found the solution yet.

http://support.microsoft.com/default.aspx?scid=kb;en-us;894179

I have also found this blog, but this did not work for me either. I have openned IE 7, Internet Options, then when I click on the Set programs button I get to the Control pannel to modify the defaults settings.



On the control pannel, once I click on the Set program access and computer defaults, I get this error:

You do not have permission to set program access and defaults




I will post when I find a solution.