|
| | | Junior Member
 
Group: Forum Members
Last Login: 7/25/2005 2:54:00 AM
Posts: 11, Visits: 1 |
| We have been using prims for our domain (900 clients) for almost a year now. Recently another domain joined our fores and we would like to service the new clients from a separate channel.
However when creating a new channel we get a login dialog box for the channel Prism_deploy_channel_creation_98.... Reinstalling the channel server has no effect. Every time a new channel is created and the same dialog box pops up (with a different Prism_deploy_channel_creation....). The existing channel can be connected every time. We are hosting the database on a windows 2000 server with sql 2000 on the same server the prism channel server is on.
We installed prism in a test environment, where everything works fine, although we used msde there. I compared the ntfs rights, user accounts and the rights within sql with the enteprise manager from sql 2000. Everything seems in order. We are kind of stuck now, any hint or tip in which direction to look for the problem would be very helpfull.
I would like to add that besides this we are very happy with prism deploy, the system works like a charm!
Danny |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: Yesterday @ 10:05:18 AM
Posts: 655, Visits: 811 |
| There are several scenarios that could cause the Prism Deploy Console to think that the Channel Creation channel (oddly enough, used to create new channels) has been secured. Try some or all of the following to restore that capability. First off, make sure that you are using Prism Deploy 6.0.3. That can be found here:
http://www.newboundary.com/products/prismdeploy/upgrade.htm 1. Reset the SQLDMO library.
a. Stop all Prism services (Prism Server, PrismXL, and Channel Deployer if it exists)
b. Uninstall Prism Deploy
c. Stop the SQL Server instance that is hosting the Prism Deploy channels
d. Delete the registry key HKEY_CLASSES_ROOT\SQLDMO.SQLSERVER
e. In a command prompt, browse to the location of the SQLDMO.DLL file and run the command "Regsvr32 SQLDMO.DLL"
f. Restart the SQL Server instance that is hosting the Prism Deploy channels
g. Reinstall Prism Deploy 2. Check to make sure that the Windows Scripting Host is installed and enabled.
a. Make sure that the files WSCRIPT.EXE or CSCRIPT.EXE exist
b. Make sure that the Default registry value in HKEY_CLASSES_ROOT\VBSFile\Shell\Open\Command\ contains a data value that points to the scripting executable in step a
c. If a or b are not true, download and reinstall the Windows Scripting Host and reinstall Prism Deploy 3. Make sure that you are using an approved version of SQL (or MSDE)
a. Open Query Analyzer or osql and run the T-SQL "SELECT @@version"
b. Make sure that it returns 8.00.760. If not, apply Service Pack 3 or greater to your instance. 4. Make sure that the Console isn't mistakenly blocking itself.
a. Browse to HKCU\SOFTWARE\Lanovation\Prism Deploy\Editor Channels\<GUID> where <GUID> is a unique value for each channel
b. Find the <GUID> for the Channel Creation channel
c. Make sure that the Secured value is set to '0' - only do this if you are sure that you did not secure your Channel Creation channel
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Junior Member
Group: Forum Members
Last Login: 7/25/2005 2:54:00 AM
Posts: 11, Visits: 1 |
| After reinstalling our server twice, the problem got even worse. Prism wouldnt install at all. We are running prism on a dell server (type 2850).
After a lot of trying and debugging, the solution was very easy. The problem was caused by the teamed network adapters. By removing the teaming prism installed again and the creation of a new channel was no problem anymore. I suspect that the nic teaming also was the reason that the channel creation failed (i will test this and post the results here).
|
| |
|
|