You might think the documentation for this would be readily available. Whereas in fact it is disparate, confusing and unclear. Here is the straightforward visual guide.
If you've been having trouble with your ISP, have some sympathy for the folks who guessed wrongest of us all... Bulldog Communications
Why in google Adwords does "Granada Television" have an activation for search cost-per-click of £2.75 and yet if you put "Granada Television" into google, you don't get a single Adwords ad?
Are Granada paying Google to inflate this price to deter advertisers scoping them?
Turned out (in my case) to be caused by onload event in body tag being assigned to a function name that had been deleted.
I deleted the function code when it was no longer necessary, but forgot to remove the attribute assignment in the body tag: < body onload = "functionname()" >
One of those errors where the message is about as helpful as a random quotation from a shakespeare sonnet.
Interestingly (or not), when I tried to reproduce the error by putting the onload assignment to a non-existent function back in, Visual Studio 2005 spotted it at compile time.
Having difficulties with the < atlas : hyperlink > ?
I mean the URL displays fine and looks like a url, but if you click it, it doesn't take you anywhere.
Looks like the text of the URL is being set correctly, but the Href is not being filled in.
This seems to be an error in the Hands on labs no. 5. - URLs display fine, but don't navigate anywhere, using the code provided in the lab.
No documentation to say what property of the
I tried: NavigateURL, Href, Alink, URL -> none of which work.
In other words what goes in place of the ????? below:
Hey Hey !!!
Nothing like good old TRIAL AND ERROR :-
Found one that worked!!! - And it looks like its CASE SeNsItIvE
ActiveSync versions prior to 4.0 wont connect to Windows Mobile 5.0 and ActiveSync versions from 4.0 onwards don't support WiFi (even though earlier versions do).
Microsoft, in their infinite wisdom, "listened to their corporate customers", who told the little poodle Microsoft that they thought ActiveSync WiFi, was a security risk, even if it is set disabled by default.
How rubbish is that!
I'm considering whether to take the 5.0 device back while I'm still inside the 14 day return period.
I spent about 2 hours altogether yesterday morning getting to the bottom of this. Its not the kind of information that Microsoft are in any kind of hurry to share with you.
But eventually a combination of looking at MSofts own documentation, HP's web site, and various other PocketPC user and developer sites including this one where I posted a couple of contributions, and I got to the bottom of it.
What a bummer!
These confirmed that versions before 4.0 will not connect to WM 5.0.
And on microsoft's web site they say if you want to use ActiveSync with WiFi you have to use versions up to 3.8. If you need this feature "use an earlier version 3.x" they happily suggest!
However no version prior to 4.0 works with WM 5.0.
So I am supposed to take a huge cut in functionality for waiting around for WM 5.0 to become available.
What a rip-off!
Maybe if we all shout loud enough, they'll put this feature back? I don't mind having to enable it in a options screen.
For goodness sake it's ridiculous!
And of course they don't advertise ahead of time that they have removed features from the newer version. They just leave that for you to find out the hard way.
Here is my advert for the new Windows Mobile 5.0:
Exciting news: Upgrade to the new Windows Mobile 5.0! - its almost as good as the previous version, except we took out one of the most useful features.
Is anyone else out there having trouble connecting to Analysis Services 2005 beta 2 from an ASP.net app on an x64 platform? Having gone through the pain of learning on this, I thought the following might be useful to someone:
The weird thing was that I didn't have any trouble when running my web app via the file system using the web server that Visual Studio 2005 creates for you on the fly. The trouble came when I tried to run the same app via IIS.
Now all of a sudden, the web server can't find the Analysis Services 9.0 provider, and returns the message "Provider cannot be found. It may not be properly installed." Well it was there a minute ago, so where has it gone?
OK, so the natural thing to think is that security account which the IIS server process is running under doesn't have visibility of the AS provider. Then you might think that a spot of impersonation, would at least confirm this is the problem, and make it go away until I can come up with a better solution that doesn't require giving the IIS process so much access.
But not a bit of it.
< identity impersonate="true" userName="XXXX" password="XXXX" />
Impersonation line in my web.config, but still I get the same error.
One thing to bare in mind, however, is that at this point I am trying to connect to AS 2005 beta 2 from ADOMD, not ADOMD.net.
I got all this legacy code, and I don't want to have to re-write it.
So I tried all kinds of endless account configurations on
(1) Analysis Services management tool
(a) Server Roles - which accounts are in the server role
(b) Adding roles and permisions to the specific cube I want to be able to access.
(2) App Pools in IIS
(3) Local Security Policy
(4) Local Users and Groups - who is a member of what groups
(5) What account the AS 2005 runs under
I suppose that I did this is a bit of an admission of my stupidity, but there we have it. None of this made any difference to my problem.
Finally surrendering to the possibility that upgrading all my code to ADOMD.net, might be the easiest thing to do
I found that I was at least getting a different error message when opening an adomd.net connection.
In fact no error when I opened the connection, instead, an error when I tried to execute a command that
pulled back a cellset:
"Either the user, WORKGROUP\MACHINENAME$, does not have access to the [DatabaseName] database, or the database does not exist."
Again switching back to running the web app through the file system using the web server instance created by Visual Studio 2005, and everything fine.
At this point I had removed my impersonation line from the web.config, and final I discover that with impersonation in place, and using adomd.net instead of adomd, I am able to connect to my Analysis Server 2005 and retrieve data, even though it is running on my local IIS.
Well the saga continued as I tried to get my Asp.net application to make calls into Office Web Components (OWC10 and OWC11). Once more, running through the file system in VS.net created web server process, everything was fine. But attempting to run the same app through IIS and I find that any attempt to reference OWC10 or OWC11 fails, with a COM error saying the components are not registered.
So here is my current conclusion - something along the following lines: On a 64-bit OS, Asp.net 2.0 can run in either 32-bit or 64-bit mode, but you have to choose - it can't do both at the same time. See the referenced article on running IIS Asp.net 2.0 in either 32 or 64-bit modes.. I have my IIS server running in 64-bit mode, but these components (OWC10, OWC11, Adomd etc.) are 32-bit components. Win64 actually automatically presents a different view of the registry to 32-bit components as opposed to 64-bit components (see article on how Win64 presents different versions of the registry to 32-bit vs. 64-bit components.) So the 32-bit web server process created on the fly by VS 2005 can see these 32-bit components, but as far as the 64-bit web IIS server process is concerned, they don't exist.
A 64-bit process cannot reference a 32-bit dll, because in-process interaction maps the referenced dll into the same process space. When I run my code through the file system and it generates a web-server process on the fly, I guess it must be making a smart choice to create a 32-bit process. Possibly it is noticing that my app is referencing 32-bit components, and automatically starting a web process using the 32-bit version of the dot net framework 2.0.
With IIS, however, the choice between 32-bit and 64-bit on a 64-bit OS has to be set ahead of time. In the first article I referrenced above it tells you how to do this. For my part with the OWC11 problem, I think I just have to wait for the 64-bit version of this to come avaialble, or create a 64-bit exe wrapper for it. I don't want to have to run my IIS in 32-bit mode throughout, just for the sake of this one feature. Either this or transfer this particular app to a different server. Or perhaps someone reading this has a better idea and could email me?
Connection isn't failing to authenticate - its failing to even find the provider. I think this means therefore, that as far as the account trying to connect is concerned, the provider hasn't been installed. The provider has been installed for the user account, but the account which is trying to connect does not seem to have the provider installed. Even with impersonation set to the user account, still not seeing it, though ??? Could it be an x64 issue? Could it be a beta2 issue?
C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\IDE\
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0\InstallDir
_______________________________============________________________
C:\Program Files (x86)\Windows CE Tools\wce500\Windows Mobile 5.0 Pocket PC SDK\ Install_files>install_script "C:\Program Files (x86)\Windows CE Tools\wce500\Win dows Mobile 5.0 Pocket PC SDK\" 0
C:\>"C:\Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe " /i "C:\Program Files (x86)\Microsoft Visual Studio 8\SmartDevices\SDK\VisualStud io\Designer\Microsoft.CompactFramework.Design.PocketPC2004.dll" Microsoft (R) .NET Global Assembly Cache Utility. Version 2.0.50215.44 Copyright (C) Microsoft Corporation. All rights reserved. Assembly successfully added to the cache C:\>"C:\Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe " /i "C:\Program Files (x86)\Microsoft Visual Studio 8\SmartDevices\SDK\VisualStud io\Designer\Microsoft.CompactFramework.Design.SmartPhone2004.dll" Microsoft (R) .NET Global Assembly Cache Utility. Version 2.0.50215.44 Copyright (C) Microsoft Corporation. All rights reserved. Assembly successfully added to the cache