We have been distributing MSDE SP3A for about 1.5 years now with our
application and about 1 month ago we started running into problems.

On a Windows 2000 SP4 machine, the following occurs:

sqlmangr.exe has generated errors and will be closed by Windows.
You will need to restart the program.
An error log is being created.

Here is what is in the Event Log after install and reboot (in this order):

Performance counters for the MSSQL$CITITECH service were loaded
successfully. The Record Data contains the new index values assigned to this
service.

The description for Event ID ( 19011 ) in Source ( MSSQL$CITITECH ) cannot
be found. The local computer may not have the necessary registry information
or message DLL files to display messages from a remote computer. The
following information is part of the event: (SpnRegister) : Error 1355.

Product: Microsoft SQL Server Desktop Engine -- Installation operation
completed successfully.

The description for Event ID ( 19011 ) in Source ( MSSQL$CITITECH ) cannot
be found. The local computer may not have the necessary registry information
or message DLL files to display messages from a remote computer. The
following information is part of the event: (SpnRegister) : Error 1355.

The application, , generated an application error The error occurred on
09/29/2006 @ 12:12:54.862 The exception generated was c0000005 at address
780104AC (wcslen)

The last one was generated by Dr Watson.

I have a little application that I installed (vb6) that goes out and gets
the list of SQL Servers. It now errors too but gives a little more
information than the sqlmangr.exe error:

-2147221499
[SQL-DMO]Code executions exception: EXEPTION_ACCESS_VIOLATION

This error comes up every time the computer is rebooted.
If I go get the latest Windows Updates, everything works fine but, this has
to be done after MSDE is installed. It does not good to have then before I
install.

More information:
On XP SP2, after I reboot, I get an error that is then asks me to send to
Microsoft. Everything works but you get the error after the first reboot.
On Win2K3 Server, everthing is OK

I usually test on VPC 2004 and have a fresh install of Win2K SP4 installed.
(And yes, I have tried on a regular PC and got the same results)

The really strange thing is that with the same VPC instance I always use
with undo disk so no changes are kept, and the same CD that worked before, I
get this error now.

(Installing, getting windows updates, then installing the rest of the
application is not an accepted answer)

I have tried everything but have given up, any would be great!

I hope I supplied enough information to . :-)

Hello Citi,

From your description, my understanding of this issue is: After you
installed MSDE, you will get the error message "sqlmangr.exe has generated
errors and will be closed by Windows." If I misunderstood your concern,
please feel free to let me know.

Based on my research, if you could start/stop and access the MSDE instance
correctly, you could ignore this error messge.

If you could not start the MSDE instance correctly, please collect the SQL
Error log files and send it to me.

By default, the error log is under folder: %Program Files%\Microsoft SQL
Server\<instance name>\MSSQL\LOG

You could zip the folder and send it to me. To get my email address, please
remove the ONLINE in my email address.

As for the Error 1355 in the eventlo, you could ignore this as SQL does not
rely on the Active Directory.

Sincerely,

Wei Lu

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
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 Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Hi ,

How is everything going? Please feel free to let me know if you need any
assistance.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

I was able to find the solution, I found an installation package that
included SP4 and this installed on all OS without issue. I also found if I
installed MDAC 2.8 first, the error did not occur.

The problem with ignoring that error is that we distribute our software to
potential customers and if they get this error everytime they start thier
PC, they are unlikely to buy our software!

Thanks for the . By the way, I inspected those logs before I submitted
an issue and there wasn't anything ful in there, I am unable to send
those now because it was on a VPC and it is gone now.

"Wei Lu [MSFT]" <weilu@online.microsoft.com> wrote in message
news:MiAPsTF6GHA.4348@TK2MSFTNGXA01.phx.gbl...
> Hi ,
>
> How is everything going? Please feel free to let me know if you need any
> assistance.
>
> Sincerely,
>
> Wei Lu
> Microsoft Online Community Support
>
> ==================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>

Brilliant!! I have been trying to solve this issue and installing MDAC
2.8 fixed my problem as well. Thank you very much :-)

CitiTech wrote:
> I was able to find the solution, I found an installation package that
> included SP4 and this installed on all OS without issue. I also found if I
> installed MDAC 2.8 first, the error did not occur.
>
> The problem with ignoring that error is that we distribute our software to
> potential customers and if they get this error everytime they start thier
> PC, they are unlikely to buy our software!
>
> Thanks for the . By the way, I inspected those logs before I submitted
> an issue and there wasn't anything ful in there, I am unable to send
> those now because it was on a VPC and it is gone now.
>
> "Wei Lu [MSFT]" <weilu@online.microsoft.com> wrote in message
> news:MiAPsTF6GHA.4348@TK2MSFTNGXA01.phx.gbl...
> > Hi ,
> >
> > How is everything going? Please feel free to let me know if you need any
> > assistance.
> >
> > Sincerely,
> >
> > Wei Lu
> > Microsoft Online Community Support
> >
> > ==================================================
> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >