------=_NextPart_0001_0BA13865
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hi Martin,
According to your dscription, the problem is that you meet the following
error when launching HIPAA 3.3 Administration tool, right?
"An error occurred in accessing the EDI Subsystem service. Make sure that
EDI Subsystem service is running and that you have network connectivity to
the server and that you have rights to access the service."
Which version of SQL Server are you using? Is it SQL 2005 or SQL 2000? If
you are using a remote SQL instance, a possible cause is that Microsoft
SQL
Server client software is not installed on the machine.
Please first make sure that the Microsoft SQL Server client software is
installed. The required SQL Client tools of HIPAA Admin include bcp.exe
and
isqlw.exe/SQLCMD.exe (sqlcmd.exe if running Sql Server 2005).
Also all of the libraries in the HIPAA install directory
\HIPAA_EDI\Subsystem\ should have permissions of read/execute for the
HIPAA
3.3 service account.
HIPAA related issues can sometimes be very complicated. If this above
isn't
the root cause, I strongly recommend you contact our Customer Sup****t
Service (CSS) or your technical account manager(TAM) to open an sup****t
incident. This will be the most effective and solid way to assist you on
such kind of issues. Honestly advices are pretty much all we have in the
newsgroup that may not be enough for complicated cases need interactions
and deep analysis.
Thanks.
Sincerely,
WenJun Zhang
Microsoft Online Community Sup****t
==================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup sup****t offering is for non-urgent issues
where an initial response from the community or a Microsoft Sup****t
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the sup****t
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Sup****t Engineer by contacting
Microsoft Customer Sup****t Services (CSS) at:
http://msdn.microsoft.com/subscriptions/sup****t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
------=_NextPart_0001_0BA13865
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit
{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0
MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Martin,
\par
\par According to your dscription, the problem is that you meet the
following error when launching HIPAA 3.3 Administration tool, right?
\par
\par "An error occurred in accessing the EDI Subsystem service. Make sure
that EDI Subsystem service is running and that you have network
connectivity to the server and that you have rights to access the service."
\par
\par Which version of SQL Server are you using? Is it SQL 2005 or SQL
2000? If you are using a remote SQL instance, a possible cause is that
Microsoft SQL Server client software is not installed on the machine.
\par
\par Please first make sure that the Microsoft SQL Server client software
is installed. The required SQL Client tools of HIPAA Admin include bcp.exe
and isqlw.exe/SQLCMD.exe (sqlcmd.exe if running Sql Server 2005).
\par
\par Also all of the libraries in the HIPAA install directory
\\HIPAA_EDI\\Subsystem\\ should have permissions of read/execute for the
HIPAA 3.3 service account.
\par
\par HIPAA related issues can sometimes be very complicated. If this above
isn't the root cause, I strongly recommend you contact our Customer Sup****t
Service (CSS) or your technical account manager(TAM) to open an sup****t
incident. This will be the most effective and solid way to assist you on
such kind of issues. Honestly advices are pretty much all we have in the
newsgroup that may not be enough for complicated cases need interactions
and deep analysis.
\par
\par Thanks.
\par
\par Sincerely,
\par
\par WenJun Zhang
\par
\par Microsoft Online Community Sup****t
\par
\par ==================================================
\par
\par Get notification to my posts through email? Please refer to:
\par
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notifications.
\par
\par Note: The MSDN Managed Newsgroup sup****t offering is for non-urgent
issues where an initial response from the community or a Microsoft Sup****t
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the sup****t
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Sup****t Engineer by contacting
Microsoft Customer Sup****t Services (CSS) at:
\par
\par http://msdn.microsoft.com/subscriptions/sup****t/default.aspx.
\par
\par ==================================================
\par
\par This posting is provided "AS IS" with no warranties, and confers no
rights.
\par
\par
\par
\par }
------=_NextPart_0001_0BA13865--
|
