Problem with Client Side Printing

After the Cumulative Security Update for Internet Explorer (912812) the client side printing doesn't work any more. Almost each client get the error:

"Unable to load client print control."

Other clients get an error with code '0x8007F304'.

What can i do? Will SP1 solve the issue?

Client Print is an Active X control. The security update may have disabled the ability to run Active X controls. Check your IE properties to see if Active X controls are allowed to run. In the patch notes I read the following.

Compatibility Patch – To help enterprise customers who need more time to prepare for the ActiveX update changes discussed in Microsoft Knowledge Base Article 912945 and included in Microsoft Security Bulletin MS06-013, Microsoft is releasing a Compatibility Patch on April 11, 2006. As soon as it is deployed, the Compatibility Patch will temporarily return Internet Explorer to the previous functionality for handling ActiveX controls. This Compatibility Patch will function until an Internet Explorer update is released as part of the June update cycle, at which time the changes to the way Internet Explorer handles ActiveX controls will be permanent. This compatibility patch may require an additional restart for systems it is deployed on. For more information, see Microsoft Knowledge Base Article 917425.

|||

i checked my internet properties and nothing has changed.

other activex controls doesn't worked any more too. for example scriptX. meadriod published a new version of their activeX control.

so how can i get it work?

|||

Launch IE

Go to Tools\Internet Options\Security\Custom Level.

In the Active X controls and plugins, select to enable. If this is already done, you may need to then go to General\Settings\View Objects and remove and then reinstall the Active X controls.

problem With 2000 client

One Winn 2000 workstatiom has problem with ACCESS 2003 ODBC conection to SQL
server on WIN 2003 server. Other clients are all WINXP. This cient is on the
different domain too. Some reports works, and some have error, ask for
password again but not accept it even if it is supplied again. Application
on other clients works well.
What can be reason for this error.
Thanks in advanced.
Hi Zeljko,
From your description, I know that when you are connecting SQL Server 2000
on Windows 2003 with your Access 2003 installed on Windows 2000
Workstation, some reports will not work proper. Have I fully understand the
issue?
Would you please give me more information for that?
1. For those cannot be opened report, do they have some common controls,
such as Combo box or Subform?
2. Will it be OK when under the same domian? (still using Access 2003 on
Windows 2000)
3. You are using ADP, isn't it? Would please please give the error message
when it ask you Login information again? or please give me more description
about asking for password
4. Have you have the latest upgrade of Windows 2000, which should be
Windows 2000 Service Pack 4
Please apply my suggestions above and let me know if this helps resolve
your problem. If there is anything more I can do to assist you, please feel
free to post it in the group
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
|||Hi Zeljko,
I am currently standing by for an update from you and would like to know
how things are going there. Should you have any questions or concerns on
the recent questions I've posted, please don't hesitate to let me know
directly. It's my pleasure to be of assistance
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
sql

problem With 2000 client

One Winn 2000 workstatiom has problem with ACCESS 2003 ODBC conection to SQL
server on WIN 2003 server. Other clients are all WINXP. This cient is on the
different domain too. Some reports works, and some have error, ask for
password again but not accept it even if it is supplied again. Application
on other clients works well.
What can be reason for this error.
Thanks in advanced.Hi Zeljko,
From your description, I know that when you are connecting SQL Server 2000
on Windows 2003 with your Access 2003 installed on Windows 2000
Workstation, some reports will not work proper. Have I fully understand the
issue?
Would you please give me more information for that?
1. For those cannot be opened report, do they have some common controls,
such as Combo box or Subform?
2. Will it be OK when under the same domian? (still using Access 2003 on
Windows 2000)
3. You are using ADP, isn't it? Would please please give the error message
when it ask you Login information again? or please give me more description
about asking for password
4. Have you have the latest upgrade of Windows 2000, which should be
Windows 2000 Service Pack 4
Please apply my suggestions above and let me know if this helps resolve
your problem. If there is anything more I can do to assist you, please feel
free to post it in the group
Sincerely yours,
Michael Cheng
Microsoft Online Support
****************************************
*******************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.|||Hi Zeljko,
I am currently standing by for an update from you and would like to know
how things are going there. Should you have any questions or concerns on
the recent questions I've posted, please don't hesitate to let me know
directly. It's my pleasure to be of assistance
Sincerely yours,
Michael Cheng
Microsoft Online Support
****************************************
*******************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.

Problem while taking script

Hi all,
I have some stored procedures in my database.
When I take script of a stored procedure using Enterprise manager from a
client system, the alignment of IF, ELSE, END,etc... are changed. They are
not in a format that I typed in query analyzer.
When I take the same script from another client system they are in proper
alignment.
Please guide me to avoid this.
Should I change any of the settings?
Thanks,
SouraHi
You may want to check what service pack has been applied to the client i.e.
check the file version of (say) one of the exes ? Try scripting from the
Object Browser in Query Analyser.
John
"SouRa" wrote:
> Hi all,
> I have some stored procedures in my database.
> When I take script of a stored procedure using Enterprise manager from a
> client system, the alignment of IF, ELSE, END,etc... are changed. They are
> not in a format that I typed in query analyzer.
> When I take the same script from another client system they are in proper
> alignment.
> Please guide me to avoid this.
> Should I change any of the settings?
> Thanks,
> Soura

Problem when launchin reportBuilder

One of our Client is using our WebApplication (ASP.NET2). In this application it is possible to lauch reportBuilder to allow reports creation. We never have any problem with this feature except today when we tried this feature on one our client computer.

Normaly when we tried this feature for the first time in a computer we get a window to allow us to install the ReportBuilder Application. So we juste have to click on run and then some plugin is installed and after that reportBuilder is working fine. When we tried to launch ReportBuilder for the time today on this computer we didn't have the choice to install the pluging but only to download it. So i've download it and put it on a folder. The i've tried to run it but the file is not associate with anything so windows ask me which program i want to use to run it. The file is called ReportBuilder.application

This is the first time this thing happened. When i was looking on this computer i've noticed that there doesn't seems to have installed any FrameWork. So i was wondering if this can be problem ? Tomorow i have to go back to find a solution for this problem so i want to know if i need to install the framework to use ReportBuilder on a Client computer?

Report Builder requires .Net Framework v2.

Problem when connect to SQL Server 2005 (SQL Native Client + Named instance)

Hi,
I have an application which previous connect to SQL Server 2000.
Now, I installed SQL Server 2005, and try to conncet to it.
The previous connection string is:
sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
In order to support SQL Native Client driver in SQL Server 2005, I
changed the connection string to:
sString.Format("Provider=SQLNCLI;
DataTypeCompatibility=80;DSN=%s;uid=%s;pwd=%s", sDb, sUser,
sPassword);
I have a default instance and a named instance in my database. So i
created two DSN:
(1) Use SQL Native Client as the driver and connect to the default
instance.
The application could work well under this configuration.
(2) Use SQL Native Client as the driver and connect to the named
instance.
The application could not work successfully under this
configuration.
It could not connect to the database.
I have started the SQL Server Browser service.
Why I could not connect to the database when i use SQL Native Client +
Named instance
Who can help me?
Thanks in advance.
Did you enable the Allow Remote Connections option? Have you run the
Surface Area Configurator and the SQL Server Configuration Manager?
Andrew J. Kelly SQL MVP
<yangrudy@.126.com> wrote in message
news:1140155887.725187.43270@.g44g2000cwa.googlegro ups.com...
> Hi,
> I have an application which previous connect to SQL Server 2000.
> Now, I installed SQL Server 2005, and try to conncet to it.
> The previous connection string is:
> sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
> In order to support SQL Native Client driver in SQL Server 2005, I
> changed the connection string to:
> sString.Format("Provider=SQLNCLI;
> DataTypeCompatibility=80;DSN=%s;uid=%s;pwd=%s", sDb, sUser,
> sPassword);
> I have a default instance and a named instance in my database. So i
> created two DSN:
> (1) Use SQL Native Client as the driver and connect to the default
> instance.
> The application could work well under this configuration.
> (2) Use SQL Native Client as the driver and connect to the named
> instance.
> The application could not work successfully under this
> configuration.
> It could not connect to the database.
> I have started the SQL Server Browser service.
> Why I could not connect to the database when i use SQL Native Client +
> Named instance
> Who can help me?
> Thanks in advance.
>

Problem when connect to SQL Server 2005 (SQL Native Client + Named instance)

Hi,
I have an application which previous connect to SQL Server 2000.
Now, I installed SQL Server 2005, and try to conncet to it.
The previous connection string is:
sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
In order to support SQL Native Client driver in SQL Server 2005, I
changed the connection string to:
sString.Format("Provider=SQLNCLI;
DataTypeCompatibility=80;DSN=%s;uid=%s;p
wd=%s", sDb, sUser,
sPassword);
I have a default instance and a named instance in my database. So i
created two DSN:
(1) Use SQL Native Client as the driver and connect to the default
instance.
The application could work well under this configuration.
(2) Use SQL Native Client as the driver and connect to the named
instance.
The application could not work successfully under this
configuration.
It could not connect to the database.
I have started the SQL Server Browser service.
Why I could not connect to the database when i use SQL Native Client +
Named instance
Who can help me?
Thanks in advance.Did you enable the Allow Remote Connections option? Have you run the
Surface Area Configurator and the SQL Server Configuration Manager?
Andrew J. Kelly SQL MVP
<yangrudy@.126.com> wrote in message
news:1140155887.725187.43270@.g44g2000cwa.googlegroups.com...
> Hi,
> I have an application which previous connect to SQL Server 2000.
> Now, I installed SQL Server 2005, and try to conncet to it.
> The previous connection string is:
> sString.Format("DSN=%s;uid=%s;pwd=%s", sDb, sUser, sPassword);
> In order to support SQL Native Client driver in SQL Server 2005, I
> changed the connection string to:
> sString.Format("Provider=SQLNCLI;
> DataTypeCompatibility=80;DSN=%s;uid=%s;p
wd=%s", sDb, sUser,
> sPassword);
> I have a default instance and a named instance in my database. So i
> created two DSN:
> (1) Use SQL Native Client as the driver and connect to the default
> instance.
> The application could work well under this configuration.
> (2) Use SQL Native Client as the driver and connect to the named
> instance.
> The application could not work successfully under this
> configuration.
> It could not connect to the database.
> I have started the SQL Server Browser service.
> Why I could not connect to the database when i use SQL Native Client +
> Named instance
> Who can help me?
> Thanks in advance.
>

Problem Using XML BASE64 encoding & SQL Server

Here is what I am trying to do.

I allow users to upload images from client side. This is the code I m using to load image into a client side xml document element

var node1 = xmlData.createElement("PHOTO");
node1.dataType = "bin.base64";
// Open stream object and read source file
adoStream.Type = 1; // 1=adTypeBinary
adoStream.Open();
adoStream.LoadFromFile(filename);

// Store file content and filename into XML nodes
node1.nodeTypedValue = adoStream.Read(-1); // -1=adReadAll
document.all("INVST_PHOTO").src = adoStream.Read(-1);
node2.nodeTypedValue = filename;

Now after that I extract this Image and insert it into Sql server using a stored procedure.

Dim ImgBuff() As Byte

ImgBuff = objDOMDocument.selectSingleNode("SACWIS/INVST/INVST_PHOTO/PHOTO").Text

' Add null termination:
ReDim Preserve ImgBuff(0 To UBound(ImgBuff) + 2) As Byte

' Get the pointer to the string:
Dim lPtrString As Long
lPtrString = VarPtr(ImgBuff(0))

objCmd.Parameters("@.pIMG_PHOTO").AppendChunk ImgBuff().

I am Sucessfully able to store it in the database fileld type of Image. Now I am using XML: to retrieve images from the database. Here is how the SQL looks like

SELECT
1 AS TAG, NULL AS PARENT,
IMG_PHOT AS [PHOTO!1!PHOTO!ELEMENT]
FROM PHOTO
FOR XML EXPLICIT , BINARY BASE64
The problem I am runing into is that content of the IMG_PHOTO are not the same after saving and retreival.

Here is how the contents are prior to inserting into database

/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAPAAA/+4ADkFkb2JlAGTAAAAAAf/bAIQABgQEBAUEBgUFBgkGBQYJCwgGBggLDAoKCwoKDBand here is how they look after retrieval

LwA5AGoALwA0AEEAQQBRAFMAawBaAEoAUgBnAEEAQgBBAGcAQQBBAFoAQQBCAGsAQQBBAEQALwA3AEEAQQBSAFIASABWAGoAYQAzAGsAQQB

I expected them to look same. I guess what I am doing is encoding the contents twice once I load it and once I am retreiving it from xml. Can please somebody help me out with this so that I can have the same content on both ocassion.

I am using Javascript/VB6/SQLServer 2000

I resolved it Instead of using

ImgBuff = objDOMDocument.selectSingleNode("SACWIS/INVST/INVST_PHOTO/PHOTO").Tex

I shoudl have used it Instead of using

ImgBuff = objDOMDocument.selectSingleNode("SACWIS/INVST/INVST_PHOTO/PHOTO").nodeTypeValue

which gives me base64 encoding data. VB string gives us Unicode data.

Problem Using XML BASE64 encoding & SQL Server

Here is what I am trying to do.

I allow users to upload images from client side. This is the code I m using to load image into a client side xml document element

var node1 = xmlData.createElement("PHOTO");
node1.dataType = "bin.base64";
// Open stream object and read source file
adoStream.Type = 1; // 1=adTypeBinary
adoStream.Open();
adoStream.LoadFromFile(filename);

// Store file content and filename into XML nodes
node1.nodeTypedValue = adoStream.Read(-1); // -1=adReadAll
document.all("INVST_PHOTO").src = adoStream.Read(-1);
node2.nodeTypedValue = filename;

Now after that I extract this Image and insert it into Sql server using a stored procedure.

Dim ImgBuff() As Byte

ImgBuff = objDOMDocument.selectSingleNode("SACWIS/INVST/INVST_PHOTO/PHOTO").Text

' Add null termination:
ReDim Preserve ImgBuff(0 To UBound(ImgBuff) + 2) As Byte

' Get the pointer to the string:
Dim lPtrString As Long
lPtrString = VarPtr(ImgBuff(0))

objCmd.Parameters("@.pIMG_PHOTO").AppendChunk ImgBuff().

I am Sucessfully able to store it in the database fileld type of Image. Now I am using XML: to retrieve images from the database. Here is how the SQL looks like

SELECT
1 AS TAG, NULL AS PARENT,
IMG_PHOT AS [PHOTO!1!PHOTO!ELEMENT]
FROM PHOTO
FOR XML EXPLICIT , BINARY BASE64
The problem I am runing into is that content of the IMG_PHOTO are not the same after saving and retreival.

Here is how the contents are prior to inserting into database

/9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAPAAA/+4ADkFkb2JlAGTAAAAAAf/bAIQABgQEBAUEBgUFBgkGBQYJCwgGBggLDAoKCwoKDBand here is how they look after retrieval

LwA5AGoALwA0AEEAQQBRAFMAawBaAEoAUgBnAEEAQgBBAGcAQQBBAFoAQQBCAGsAQQBBAEQALwA3AEEAQQBSAFIASABWAGoAYQAzAGsAQQB

I expected them to look same. I guess what I am doing is encoding the contents twice once I load it and once I am retreiving it from xml. Can please somebody help me out with this so that I can have the same content on both ocassion.

I am using Javascript/VB6/SQLServer 2000

I resolved it Instead of using

ImgBuff = objDOMDocument.selectSingleNode("SACWIS/INVST/INVST_PHOTO/PHOTO").Tex

I shoudl have used it Instead of using

ImgBuff = objDOMDocument.selectSingleNode("SACWIS/INVST/INVST_PHOTO/PHOTO").nodeTypeValue

which gives me base64 encoding data. VB string gives us Unicode data.

Problem using SELECT statement on Access Column Name

Im writing a VB program that queries an MS Access db. The column name is CONTACT#. Using the SQL statement...
"SELECT * FROM CLIENT WHERE CONTACT# = '1'"
Produces an error. I cannot change the name of the column name is there anyway around this?Try this:
SELECT * FROM CLIENT WHERE [CONTACT#] = '1'
:eek:

Problem using Client Tools to Remotely Connect to a SQL Server Instance on Anoth

Someone please help me before I loose all of my hair :mad: !!!

I have two machines, a Windows Server 2003 machine running an SQL Server Standard Edition database instance and client tools (Enterprize Manager etc.), and a workstation PC running Windows XP SP2 which has just the SQL Server client tools (not an actual DB instance).

I'm trying to use the Enterprize Manager client tool on my WinXP machine to remotely connect to the server instance on the server PC (via 'New SQL Server Registration' option). Everytime I do this I get the following error message:

Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server Connection.

Now I've tried using different usernames and passwords. I have login details for my SQL Server set to use Windows Login rather then SQL Server login, so I tried remotely connecting with the username and password for the server PC, tried 'sa' with server password, even tried setting up a new user on the server and logging in from the client with that, no luck. I've opened up correct ports 1433 on both PCs, even disabled the windows firewalls algother. Both server and client have SP3a installed, WinServer2003 has SP1 and XP SP2.

So I'm at a loss to how to remotely connect to my SQL Server. FYI I know the server itself is working fine because I can connect to it using Enterprize Manager/Query Analyser on the local machine. Any ideas? Many thanks for your help!If the client and the server are on the same domain, or if the client account belongs to the tree where domain belongs to, then you can use Windows authentication. But if you already tried this, can you do a TELNET from the client with 1433 successfully?|||I've not setup a Domain Controller. Anyway I've solved it, I had SQL Server running in Windows Authentification Mode, so I switched to mixed mode and all is well now :)