iOS: Device not recognized in iTunes for Mac OS X

My iPod Touch and iPad suddenly didn’t get recognized in iTunes anymore.

The USB connection was fine since the battery symbol on my iPod Touch indicated that it was charging.

I recently updated to Mac OS X 10.7 Lion and deleted the old Xcode and then installed the new Xcode. (I also renamed my /usr/local/ directory and installed Homebrew, but this should not have affected iTunes at all.) My computer seems to be working just fine besides some Safari crashes. But my devises don’t show up in iTunes anymore.

I follow the steps in iOS: Device not recognized in iTunes for Mac OS X and Mac OS X v10.6 or later: iOS device not recognized in iTunes after restart and iTunes: How to remove and reinstall the Apple Mobile Device Service on Mac OS X but couldn’t delete iTunes as described in Removing iTunes for Mac OS X because I got following error message: “iTunes.app can’t be modified or deleted because it’s required by Mac OS X”. How To: Delete iTunes in Lion worked just fine.

Now iTunes is recognizing and syncing again.

Leave a Comment

Updating Custom Functoids in the Visual Studio 2005 Toolbox

Updating custom functoids that you developed in external assemblies (for your BizTalk Server 2006 maps) can be a pain in Visual Studio 2005. Visual Studio does not really support it and it is very slow.

Here is what you have to do after you just changed something in your custom functoid (e.g. something in the resource file):

  1. Build your custom functoid project. 
  2. Copy the DLL into C:\Program Files\Microsoft BizTalk Server 2006\Developer Tools\Mapper Extensions\
  3. Delete the old DLL from your GAC (“C:\WINDOWS\assembly\” )
  4. Add the new DLL into your GAC
  5. Do NOT waste your time with right clicking in your Functoids Toolbox to select “Reset Toolbox”. This only works the very first time for new functoid assemblies. Instead, follow the next steps:
  1. Close Visual Studio 2005
  2. Delete all four toolbox*.tbd files in “C:\Documents and Settings\hyyees1\Local Settings\Application Data\Microsoft\VisualStudio\8.0″ 
  3. Open up Visual Studio 2005 again
  4. Open the Functoids Toolbox again (you may have to open a map first). This will take about a minute or two since Visual Studio 2005 has to recreated the deleted toolbox*.tbd files again.
    That is it. It is not very convenient but it works 100%.

This information is based on

I hope that this will make your development life easier.

Leave a Comment

Error with BizTalk Server 2006 SQL Adapter

I just had a problem in BizTalk Server 2006. And since I couldn’t find a solution to it on the Internet I decided to post it here after I found out how to fix it!

Problem:
The problem is with the SQL Adapter. The SQL Adapter wizard would crash/disappear after I selected “Stored Procedure” and hit next. It never showed me the screen where I could select what Stored Procedure to use.

My setup:
-Windows XP with SP2
-Visual Studio 2005 Team Edition for Software Developers with SP1
-Microsoft HotFix kb918642 (see below why I installed it)
-BizTalk Server 2006 Developer Tools only (I didn’t have the complete server installed on my local computer!)

How to re-created the problem:
-> BizTalk Project
-> Add
-> Add Generated Items…
-> Add Adapter Metadata
-> I selected my remote computer which is our BizTalk production environment
-> Set connection string to the DB I want to use (be sure to check the “Allow saving password” if you “Use a specific user name and password”!)
-> Select Send port and provide all the values
-> Select Stored Procedure
==> Now the wizard just crashes/disappear when selecting Next

Different databases:
I tried creating a new database with one simple table containing only an int and a char(10) field and a simple stored procedure to insert into this table in three different environments, and none worked!:
-Remote SQL Server 2000 SP4
-Remote SQL Server 2005 SP1
-Local SQL Server 2005 Express (from Visual Studio 2005 with SP1)

Avoid unsupported data types:
I also made sure that my database didn’t have any table with a data type:
-varbinary(MAX)
-varchar(MAX)
-nvarchar(MAX)
-xml
data type because BizTalk Server 2006 doesn’t support this. The error description by Microsoft makes this look just like the error I was getting, but it seems to be a different and unrelated one: http://support.microsoft.com/kb/917847 . This issue is also described at: http://msdn2.microsoft.com/en-us/library/aa578440.aspx

Event Log errors (shim database):
I checked my Event Log and found following error:
“Unable to open shim database version registry key – v2.0.50727.00000.”Installing KB918642 http://support.microsoft.com/kb/918642 got rid of this error in the event log, but didn’t solve my problem. You may want to use “Process Monitor” to verify if you have this problem: http://www.microsoft.com/technet/sysinternals/processesandthreads/processmonitor.mspx

How I fixed it:
Some people mentioned that they had the same problem as I had on one computer but not on another.
I therefore decided to install the complete BizTalk Server 2006 software on my computer and not just the Development Tools.
I uninstalled SQL Server 2005 Express, BizTalk Server 2005 Standard Edition, Enterprise Single Sign-On.
I then installed SQL Server 2005 Developer Edition, BizTalk Server 2006 Developer Edition (with Enterprise Single Sign-On as a Master Server).
Now I have my own development environment on my own computer.

The result:
Running the SQL Adapter wizard works now without a problem; the SQL Transport Schema Generation Wizard does NOT close unexpectedly in BizTalk Server 2006 anymore! And the strange thing is that I don’t even use any of my new local SQL Server or BizTalk Server! I’m still using my production BizTalk Server 2006 environment which is on a different computer with a SQL Server DB on yet another computer…

Summary:
I assume that installing the complete BizTalk Server 2006 software instead of just the Developer Tools on my local computer (my local computer is the only one with Visual Studio) must install some extra pieces of software that is required to run the SQL Adapter wizard. And without that, it just crashes without any information in the Event log.

I hope that this is helpful and not too complicated.

Leave a Comment