Occasionally when the site gets loaded the error below occurs.  Any
idea as to how to prevent this?  Only way to clear the error is to
recycle the application farm.  Site is Commerce 2002 SP2 on Windows
2003.


Microsoft VBScript runtime error '800a01fb'

An exception occurred: 'MSCSProfileService.GetProfileByKey'

/commerce/include/std_profile_lib.asp, line 179

[ Post a follow-up to this message ]

I get the same error, with the same setup. Were you able to solve it?
If I clear the cookie, it will work again, but will break again if the
browser is shut down, possibly under other conditions as well.

I have 2 other CS2002 sites on the box, and they don't exhibit the
problem. I think I have them configured similarly, so I am fairly
stumped. Thanks.

Joe wrote:
> Occasionally when the site gets loaded the error below occurs.  Any
> idea as to how to prevent this?  Only way to clear the error is to
> recycle the application farm.  Site is Commerce 2002 SP2 on Windows
> 2003.
>
>
> Microsoft VBScript runtime error '800a01fb'
>
> An exception occurred: 'MSCSProfileService.GetProfileByKey'
>
> /commerce/include/std_profile_lib.asp, line 179

[ Post a follow-up to this message ]

Update:
I'm now not so sure that the cookie is the problem. The following line
is preventing me from even logging into the site.

Set rsGetProfile = MSCSProfileService.GetProfile(sProfileID,
sProfileType, RETURN_NOTHING_ON_NO_PROFILE)

The GetProfile call is blowing up, but I have already established that
the MSCSProfileService object is instantiated and has a valid
connection string.

The ever-helpful error message is as follows:

Microsoft Commerce OLE DB Provider error '80040e14'

One or more errors occurred during processing of command.

/catalog/include/std_profile_lib.asp, line 329

[ Post a follow-up to this message ]

I fixed it. It turns out that bizdesk by default had the following
fields in the user profile object: u_addresses, s_language. They did
not exist in the Userobject table. Once I removed those fields from the
profile definition and restarted commerce server, things worked.

That problem would have probably been avoided if bizdesk actually
functioned.:|

[ Post a follow-up to this message ]