elsuizo¥j賡جrë,Š‰ìš+¢ÊµÊ&

Hi to all
I try to install this Notification Workflow SA. Followed the instructions in
do***entation as well as in KB894486, to no avail.
When I start from scratch, e.g. without DB tables, they are created, then
Setup stops with same message as do***ented on the screen shot in the
installation guide.
When trying again, it takes not as long and the script file in the command
window lists quite some data which I cannot capture, too quick. Then, the
error message and after I click ok, the rollback.
It does not come to any logging, except from:
Error 1001. Installation of Notification Workflow Application failed.
=== Logging stopped: 02.12.2005 16:12:38 ===

The landscape is:
Win2k3 standard eng
SQL 2000 SP3 on same machine
Reporting Services on same machine

I'll be grateful for any hint.
elSuizo

pete zerger

Hello elSuizo,

In addition, you'll need to have installed

SQL Notification Services with SP1
SQLXML SP2 or SP3
SOAP Toolkit 3.0

Do you have these installed already?

Notification Workflow SA (NWSA) will install databases on your MOM database
server, and overall I've found the install less complex if you put all components
of the SA on that box, although I have performed a distributed install with
the website component on my MOM Reporting Server.

Hope this helps. Post an update if problems persist and we'll continue troubleshooting

Regards,

Pete Zerger, MCSE (Messaging)
BLOG: http://www.it-jedi.net/

elsuizo¥j賡جrë,Š‰ìš+¢ÊµÊ&

thank you for offering me your help, Pete. Excuse me for not having been
enough accurate in the 1st post; Yes, I have all this stuff installed. Got
the list from some article, also mentioning MDAC 2.8 as a prereq. But I
assume this is included in win2k3.
This is a MOM all-in-one server, no other parts on other machines. MOM works
fine so far. Are there places to look for information, as the SA doesn't log
anything?
Cheers
+

pete zerger

Hello elSuizo,

Sorry so long in replying to your message.

A couple of thoughts. If you have attempted before and deleted the databases
in Enterprise Manager, go to the physical directory and delete the .mdf and
..ldf files themselves, as they dont seem to be deleted always and their presence
causes install failure in my experience.

Also, make sure CScript is your default scripting engine - from a cmd line,
type 'cscript /H:cscript' (without quotes) to set it as default.

Let me know if any change. I am building an installation walkthough that
I'll be finished with in a day or so that I can forward to you if no improvement
in the situation.

Regards,

Pete Zerger, MCSE (Messaging)
BLOG: http://www.it-jedi.net/

pete zerger

Hello elSuizo,

As promised, I put together an ad-hoc installation walkthrough for the Notification
Workflow Solution Accelerator that brings together information from multiple
guides and adds some of my own troubleshooting data. I've installed about
4 times now, so I've got most of the bugs worked out I think. This assumes
installation on the MOM database server, so if you're in a single server
environment, this should do the trick.

Just follow the instructions in order and contact me through the group or
offline at my personal e-mail address.

http://www.it-jedi.net/HOW-TO/NWSA/NWSA.htm


Regards,

Pete Zerger, MCSE (Messaging)
BLOG: http://www.it-jedi.net/

elsuizo¥j賡جrë,Š‰ìš+¢ÊµÊ&

first time, the setup of NWSA executed without interruption.
Alas, there is some more obstacle in registering the modified appconfig.xml;
when I run the command, I get the error that the utility would not recognise
the second parameter, basePath. Is it possible I made an error modifying the
file? I copy it here:
<?xml version="1.0" encoding="utf-8"?>
<NotificationServicesInstance xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.microsoft.com/MicrosoftNotificationServices/ConfigurationFileSchema">
<InstanceName>NotificationWorkflow</InstanceName>
<SqlServerSystem>%SqlServer%</SqlServerSystem>
<Applications>
<Application>
<ApplicationName>NotificationWorkflowApp</ApplicationName>
<BaseDirectoryPath>%BaseDirectoryPath%\AppDefiniti on</BaseDirectoryPath>
<ApplicationDefinitionFilePath>appADF.xml</ApplicationDefinitionFilePath>
<Parameters>
<Parameter>
<Name>_DBSystem_</Name>
<Value>%SqlServer%</Value>
</Parameter>
<Parameter>
<Name>_BaseDirectoryPath_</Name>
<Value>%BaseDirectoryPath%</Value>
</Parameter>
<Parameter>
<Name>_NSSystem_</Name>
<Value>%NSSystem%</Value>
</Parameter>
</Parameters>
</Application>
</Applications>
<DeliveryChannels>
<DeliveryChannel>
<DeliveryChannelName>EmailChannel</DeliveryChannelName>
<ProtocolName>SMTP</ProtocolName>
<Arguments>
<Argument>
<Name>SmtpServer</Name>
<Value>s01.asp.local</Value>
</Argument>
<Argument>
<Name>BodyEncoding</Name>
<Value>utf-16</Value>
</Argument>
</Arguments>
</DeliveryChannel>
</DeliveryChannels>
</NotificationServicesInstance>

Thanks again.
+
"Pete Zerger" wrote:

pete zerger

elSuizo,

Excellent. I am afraid I initially posted an earlier revision of the guide
in error. I noticed this after the fact and reposted the final version.
Please execute the following and you should be set. If not, post the errors
to the group and we'll get you up and running.

#1 - Change This:
<Name>BodyEncoding</Name>
<Value>utf-16</Value> --This is the wrong character set!

to this:
<Name>BodyEncoding</Name>
<Value>utf-8</Value>

#2 - Repeat the update sequence as follows (cut and paste to command line)
as there was a small error in the BaseDirectoryPath in the old version I
posted.
Changes to the AppConfig.xml file must be registered with the Notification
Workflow application itself using a SQL Notification Services command line
tool called NSCONTROL. For more info on NSCONTROL, see SQL Notification
Services Books Online


1.. The application must be disabled prior to being updated. Disable
Notification Workflow by entering the following at the command line:

NSCONTROL DISABLE -name "NotificationWorkflow"

2.. Now, we can register the changes made to the AppConfig.xml file. Copy
the following to a command prompt (single line) and press enter. Be sure to
replace <server> with the name of the appropriate server - in this case, the
name of the MOM database server.

NSCONTROL UPDATE -in "C:\Program Files\Microsoft\Notification
Workflow\Notification Workflow\AppDefinition\appconfig.xml"
SQLServer=<server> BaseDirectoryPath="C:\Program
Files\Microsoft\Notification Workflow\Notification Workflow"
NSSystem=<server> -verbose -force


3.. When complete, re-enable the application with the following command.
NSCONTROL ENABLE -name "NotificationWorkflow"

When you test delivery for the first time, load the NS$NotificationWorkflow
Perfmon object and watch the batch and notification delivery failure and
success counters, and also the Application Event Log for errors.

This should do the trick. If not, post the errors and we'll work through it.
Good luck!

Kind Regards,

Pete Zerger, MCSE (Messaging)
BLOG: http://www.it-jedi.net/

elsuizo¥j賡جrë,Š‰ìš+¢ÊµÊ&

Pete
We are getting closer, thanks to your help!
Now I can set up the command to register appconfig.xml, but I get the answer
that it can't access the SQL Database. Here is the dialog:

C:\Do***ents and Settings\administrator.ASP>"\Program Files\Microsoft SQL
Server
Notification Services\v2.0.3008.0\Bin\NSControl.exe" UPDATE -in "C:\Program
Fil
es\Microsoft\Notification Workflow\Notification
Workflow\AppDefinition\appconfig
..xml" SQLServer=s03.asp.local BaseDirectoryPath="C:\Program
Files\Microsoft\Noti
fication Workflow\Notification Workflow" NSSystem=s03.asp.local -verbose
-force

Microsoft Notification Services Control Utility (Standard) (SP1) 2.0.3008.0
Copyright (C) Microsoft Corporation 2003. All rights reserved.

Notification Services failed to open a connection to SQL Server.
ServerName: s03.asp.local
DatabaseName: NotificationWorkflowNSMain
SqlServerError:
Source: .Net SqlClient Data Provider
Number: 2
State: 0
Class: 20
Server:
Message: An error has occurred while establishing a connection to
the se
rver. When connecting to SQL Server 2005, this failure may be caused by the
fac
t that under the default settings SQL Server does not allow remote
connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL
Server)
Procedure:
Line Number: 0

Do you see a way around this? I've done all this as a domain admin who has
any perms also on MOM and SQL.
Looking forward to get more help from you.
elsuizo

pete zerger

elSuizo,

We're getting closer. Yes, this does ring a bell. I think perhaps TCP/IP is
not enabled for SQL connections. Perform the following steps please:
Goto Start --> Run. In the Run box, type 'cliconfg' (without the quotes)
and press enter. This will launch the SQL Client Network Utility.

Make sure both Named Pipes and TCP/IP are listed in the right hand box
'Enabled Protocols by order'.

Run the NSCONTROL command again and see if it is successful this time.

Let me know if any questions about this procedure. Post again to let me
know if this helps. Good luck!

--
Regards,

Pete Zerger, MCSE (Messaging)
pete.zerger@nospam.gmail.com
BLOG: http://www.it-jedi.net/

elsuizo¥j賡جrë,Š‰ìš+¢ÊµÊ&

Pete, I don't succeed; followed your instructions, CliConfg already with
Named Pipes and TCP/IP. Repeated everything:
-stop service
-disable application
-nscontrol update ...
-start service
-enable application

alas, no better.
restart server (remember, all-in-one box): all remains the same, NSCONTROL
brings same answer quoted in previous post.
What else can I do now?
Regards
elSuizo