Microsoft Agent Within SharePoint
We wanted to utilize the Microsoft Agent API to provide interactive help within our MOSS deployment. Since we are using JavaScript, we thought it would be best to put the code within an HTML page exposed within MOSS via a web part.
The problem -- we get ActiveX warnings for each of the controls (two agent characters, the Agent server engine, and the TTS engine) but no dialog box pops up through the web part.
Trying to find a way to deactivate the alerts within MOSS so that the agent scripting will run. Coming up with blanks so far.
Would appreciate any assistance.
thanks!
Answers
- Try using the agents within a regular HTML page (on a different website). See if you can fix the errors that arise there, and then apply the same fix to your SharePoint environment. I suspect the ActiveX controls are not installed locally on the client machine.
All Replies
- Have you tried added the site to your Local Intranet zone?
Yes... also tried trusted zone. Same problem.
We may try stripping all security off the server while in the lab to see if it works, and then we can incrementally rebuild security around the issue... MAYBE.
But any other tips will be appreciated.
- Just read the post again. Are you using the Page Viewer WebPart? If so, the site you are linking to needs to be in your Local Intranet zone as well.
- Everything is all on the same site... all in the trusted intranet zone.
- Trusted zone is not the same as Local Intranet zone. Please verify you have added this to the Local Intranet zone.
Excuse my poor wording. The site is in the local intranet zone.
When I open the HTML file for editing in SharePoint Designer, I get four ActiveX warnings -- presumbably two for AgentControl and two for L&H TTS.
When opening the file in browser, there is no warning, just an error that "'AgentControl.characters' is null or not an object" for the page.
When trying to open it via hyperlink, SharePoint supresses the error but nothing happens.
- Try using the agents within a regular HTML page (on a different website). See if you can fix the errors that arise there, and then apply the same fix to your SharePoint environment. I suspect the ActiveX controls are not installed locally on the client machine.
