Внутренняя ошибка visio 3400 действие 1005

RRS feed

  • Remove From My Forums
  • Question

  • I am getting ERROR 3400 Action 1005 in VISIO 2010! Can You help me fix this?

Answers

  • What are you doing to get this? Some background information would be very helpful.


    Chris Roth Visio Guy (http://www.visguy.com) Please check Mark as Answered if I’ve answered your question and solved your problem. If you found my post helpful, please click Vote as Helpful.

    • Marked as answer by
      Jennifer Zhan
      Thursday, April 21, 2011 2:19 AM

All replies

  • What are you doing to get this? Some background information would be very helpful.


    Chris Roth Visio Guy (http://www.visguy.com) Please check Mark as Answered if I’ve answered your question and solved your problem. If you found my post helpful, please click Vote as Helpful.

    • Marked as answer by
      Jennifer Zhan
      Thursday, April 21, 2011 2:19 AM

  • I recieved the same error message.

    I attempted to take my Viso 2010 drawing .vsd and then Save As PDF then recieved this error message:

    «Visio internal error: 3400
    Action 1005: Save As

    First try closing and reopening the file. Next try restarting Visio.»

    I closed then reopened and this did not help.  I also closed Visio 2010 and reopen and this did not help.

    Please help.

    Thx.

  • So, can you still open the file?

    If so then can you do a Save As in a different format, like GIF? I know you want PDF but this just to check what is happening.

    Are you able to create a new diagram, then save that as PDF?

    If the PDF save error still occurs what is the path you are saving to?


    — Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.

  • Yes, I am still able to open, edit the file as a .vsd file and I can close the file and save the files as a .vsd.  I am able to save each sheet as a .gif file.  I am NOT able to save the .vsd file as a .pdf.  I recieve the error message listed
    above.

    I am able to create a new digram drawing file (.vsd), when I attempt to take the new diagram and save it as a .pdf file, I recieve the same error message.  The path I attempt to save the .pdf file to is my desktop — C:\Users\____\Desktop.

    Please help.  Thx.

  • I assume you have tried saving to some other path …


    — Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.

  • Yes, when I attempt to save it as a PDF to a different path I receive the same error. 

  • There are many other PDF creator applications available (some free, some not), might be worth a try.


    — Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.

  • Hi Adam,

    Do you run, and have you installed Office Service Pack 1 for 2010?

    I am getting the same error and it appears to have started at around the same time as I installed SP1 for Office 2010.

    SP1 appears to have stomped on the Adobe addins as the Adobe printer also showed some strange characteristics.

    I reinstalled Adobe Acrobat Pro X and the PDF printer started to behave correctly but the #3400 error still persisted.

    Anything in common here?

  • I ran into this, and it turned out to be a permissions issue on the t2embed.dll file. Granting users read access to this file cleared up my issue. I made the change on a Windows 7 box using the following method.

         takeown /f c:\Windows\System32\t2embed.dll
         icacls.exe c:\windows\system32\t2embed.dll /grant *S-1-5-11:(GR)

    Hope that helps someone…

  • I get the same error.

    I checked the permissions and they are fine.

    @Oldguard, you used takeown to take ownership so the file no longer belongs to the Trausted Installer, which is what it is originally. Is this a good idea?

    I am creating a PDF to use with a desktop publishing program and every other image file is rendered as crap when imported into my DTP.

    I tried PNG at 600 DPI, TIF at 600 DPI. WMF is very checkered and emf came in as all black icons.

  • Run a Repair from Programs and Features. 

    • Proposed as answer by
      Grant Bowen
      Monday, September 17, 2012 5:58 PM

  • I got the same error. Everything seemed to work just fine, except Save As PDF.

    At last I found that removing an imported picture (copy from other Visio drawing and originaly extracted from a screenshot) from de drawing
    solved the problem. Suddenly I could Save As PDF again.

    I tried to save older drawings with the same inserted pictures, and the problem returned.

    Strangely, there are also other pictures inserted and they do not cause any problems.

    Somehow the picture isn’t recognized as a Visio object.

    A little workaround fixed the problem:

    I copied the picture into MS Word. Than right-click the picture and chose: Visio object/convert.

    Chose Convert to Visio object and apply. You get a message like “object is definitely converted to a Visio object”.

    When finished, copy the picture back into the Viso-drawing. It’s no problem saving it as a PDF anymore.

  • I tried this but to no avail

    still can’t save to pdf???!!!

  • I found a solution on my computer!!!!

    Dell Inspiron15 3521 running Win7 Pro

    When trying to save to PDF: before saving, go to «options» and
    uncheck
    box «ISO 19005-1 compliant PDF/A»

    This worked for me an I can save to PDF’s once again. I don’t know how this got changed?? Maybe with a recent update???? 

    • Proposed as answer by
      easy gonzales
      Friday, May 8, 2015 8:37 PM

  • This work for me as well.  thanks a lot.

RRS feed

  • Remove From My Forums
  • Вопрос

  • I am getting ERROR 3400 Action 1005 in VISIO 2010! Can You help me fix this?

Ответы

  • What are you doing to get this? Some background information would be very helpful.


    Chris Roth Visio Guy (http://www.visguy.com) Please check Mark as Answered if I’ve answered your question and solved your problem. If you found my post helpful, please click Vote as Helpful.

    • Помечено в качестве ответа
      Jennifer Zhan
      21 апреля 2011 г. 2:19

Все ответы

  • What are you doing to get this? Some background information would be very helpful.


    Chris Roth Visio Guy (http://www.visguy.com) Please check Mark as Answered if I’ve answered your question and solved your problem. If you found my post helpful, please click Vote as Helpful.

    • Помечено в качестве ответа
      Jennifer Zhan
      21 апреля 2011 г. 2:19

  • I recieved the same error message.

    I attempted to take my Viso 2010 drawing .vsd and then Save As PDF then recieved this error message:

    «Visio internal error: 3400
    Action 1005: Save As

    First try closing and reopening the file. Next try restarting Visio.»

    I closed then reopened and this did not help.  I also closed Visio 2010 and reopen and this did not help.

    Please help.

    Thx.

  • So, can you still open the file?

    If so then can you do a Save As in a different format, like GIF? I know you want PDF but this just to check what is happening.

    Are you able to create a new diagram, then save that as PDF?

    If the PDF save error still occurs what is the path you are saving to?


    — Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.

  • Yes, I am still able to open, edit the file as a .vsd file and I can close the file and save the files as a .vsd.  I am able to save each sheet as a .gif file.  I am NOT able to save the .vsd file as a .pdf.  I recieve the error message listed
    above.

    I am able to create a new digram drawing file (.vsd), when I attempt to take the new diagram and save it as a .pdf file, I recieve the same error message.  The path I attempt to save the .pdf file to is my desktop — C:\Users\____\Desktop.

    Please help.  Thx.

  • I assume you have tried saving to some other path …


    — Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.

  • Yes, when I attempt to save it as a PDF to a different path I receive the same error. 

  • There are many other PDF creator applications available (some free, some not), might be worth a try.


    — Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.

  • Hi Adam,

    Do you run, and have you installed Office Service Pack 1 for 2010?

    I am getting the same error and it appears to have started at around the same time as I installed SP1 for Office 2010.

    SP1 appears to have stomped on the Adobe addins as the Adobe printer also showed some strange characteristics.

    I reinstalled Adobe Acrobat Pro X and the PDF printer started to behave correctly but the #3400 error still persisted.

    Anything in common here?

  • I ran into this, and it turned out to be a permissions issue on the t2embed.dll file. Granting users read access to this file cleared up my issue. I made the change on a Windows 7 box using the following method.

         takeown /f c:\Windows\System32\t2embed.dll
         icacls.exe c:\windows\system32\t2embed.dll /grant *S-1-5-11:(GR)

    Hope that helps someone…

  • I get the same error.

    I checked the permissions and they are fine.

    @Oldguard, you used takeown to take ownership so the file no longer belongs to the Trausted Installer, which is what it is originally. Is this a good idea?

    I am creating a PDF to use with a desktop publishing program and every other image file is rendered as crap when imported into my DTP.

    I tried PNG at 600 DPI, TIF at 600 DPI. WMF is very checkered and emf came in as all black icons.

  • Run a Repair from Programs and Features. 

    • Предложено в качестве ответа
      Grant Bowen
      17 сентября 2012 г. 17:58

  • I got the same error. Everything seemed to work just fine, except Save As PDF.

    At last I found that removing an imported picture (copy from other Visio drawing and originaly extracted from a screenshot) from de drawing
    solved the problem. Suddenly I could Save As PDF again.

    I tried to save older drawings with the same inserted pictures, and the problem returned.

    Strangely, there are also other pictures inserted and they do not cause any problems.

    Somehow the picture isn’t recognized as a Visio object.

    A little workaround fixed the problem:

    I copied the picture into MS Word. Than right-click the picture and chose: Visio object/convert.

    Chose Convert to Visio object and apply. You get a message like “object is definitely converted to a Visio object”.

    When finished, copy the picture back into the Viso-drawing. It’s no problem saving it as a PDF anymore.

  • I tried this but to no avail

    still can’t save to pdf???!!!

  • I found a solution on my computer!!!!

    Dell Inspiron15 3521 running Win7 Pro

    When trying to save to PDF: before saving, go to «options» and
    uncheck
    box «ISO 19005-1 compliant PDF/A»

    This worked for me an I can save to PDF’s once again. I don’t know how this got changed?? Maybe with a recent update???? 

    • Предложено в качестве ответа
      easy gonzales
      8 мая 2015 г. 20:37

  • This work for me as well.  thanks a lot.

niceguy1978


  • #1

Dear MS staff:

I get this weird error with Visio 2003 when saving a visio file containing
a Microsoft equation editor object:

**************************************************
Visio internal error:#3400
Action 1004: Save
First try closing and reopening the file. Next try restarting Visio
**************************************************
Both the suggestions (closing and reopening, and restarting visio) do not
help.

More information regarding the problem:
1) This problem happens only when an equation editor object is present in
the visio file. I am able to save the visio file when I delete the equation
editor letters/objects.

2) I do not face this problem in a word file. So the problem, I think, is
only with visio and not with the equation editor.

3) I have reinstalled visio, but the problem remains

4) I have reinstalled the MSoffice 2003 and visio together. But the problem
still remains.

I am not able to find a solution to this problem in the web, though it has
been mentioned once in a website (lockergnome). I have wasted a lot of time
trying to fix this problem. I would appreciate any help in solving this
problem.

Sincerely,
lal

Advertisements

Aaron Rykhus [MSFT]


  • #2

Does this happen on new/blank Visio drawings (File/New/New Drawing) with
new Equation Editor 3.0 object (Insert/Object…/Equation Editor 3.0) or
just existing drawings with existing equation editor objects?

Are the equations off the page at all, and onto the scratch area (gray
space)?

Are you using the service packs for Office 2003 and Visio 2003? (currently
service pack 3)

Best Regards,

Aaron Rykhus, MCP, MCDST
Online Support Engineer
Microsoft Corporation

niceguy1978


  • #3

Dear Mr. Rhykhus,

Thanks for your reply. Let me answer your questions:
Question #1:
Does this happen on new/blank Visio drawings (File/New/New Drawing) with
new Equation Editor 3.0 object (Insert/Object…/Equation Editor 3.0) or
just existing drawings with existing equation editor objects?

Answer for Q#1: It happens whenever an equation editor object is
added to the visio file. The visio file can be a new one containing no
equation editor object at all or can be a old one already containing
an equation editor object. In the latter case, the file is created in power
point
with equation editor object and then later pasted in visio as a ‘group’;
i.e., as
an image in visio.

Question#2:
Are the equations off the page at all, and onto the scratch area (gray
space)?
Answer for Q#2: The equations are on the same page and on the figure
itself. For example, consider naming a specific part in the figure, such as
a node in a circuit, by a symbol, such as ‘i’. You place this symbol close to
the specific part of the figure.

Question#3:
Are you using the service packs for Office 2003 and Visio 2003? (currently
service pack 3)
Answer for Q#3: I think I have them installed once I got this error. But I
will
check for this one more time.

I found a way to get around the problem, but I still would like to solve the
my problem.
Way around the problem:
1) Create the figure without any equation editor object in visio.
2) Copy the figure onto powerpoint.
3) Insert the equation editor object to the figure in powerpoint. There is
no problem in this.
4) Group the figure with equation editor objects in powerpoint and copy the
grouped item onto visio
5) Save as grouped item as a visio file or as any other file .tif as you like

I would appreciate if you could reply with your suggestions.

Sincerely,
niceguy

Aaron Rykhus [MSFT]


  • #4

Could you reply with an exact set of steps you take to get the error so I
can try to reproduce the problem on my end?

Best Regards,

Aaron Rykhus, MCP, MCDST
Online Support Engineer
Microsoft Corporation

niceguy1978


  • #5

Dear Mr. Rykhus,

The following sequence of steps creates the error in my system:
1) Invoke visio2003 and create a new .vsd file
2) Put a visio object in the file. I had put a resistor (Basic Electrical
Engineering
diagram option in visio)
3) Save the visio file (Note: this save was successful for me)
4) Insert an equation editor object (Insert/Object/Microsoft Equation Editor/)
I added a symbol ‘i’ from the equation editor. The place in the figure
where
this symbol is added is not important.
5) Try saving this file now. I am not able to save the file now. Instead, I
get the
visio error at this time:
**************************************************
Visio internal error:#3400
Action 1004: Save
First try closing and reopening the file. Next try restarting Visio
**************************************************
Sincerely,
niceguy

Aaron Rykhus [MSFT]


  • #6

I still don’t get the error when saving, based on your steps here’s what I
did on my Windows XP machine:

1. Start Visio Professional 2003, click on the File menu, point to New,
click New Drawing (US Units)
2. Click on the File menu, point to Shapes, point to Electrical
Engineering, click Fundamental Items (US Units). Drag and drop a Resistor
shape from the Shapes window onto the middle of the page.
3. Click the File menu and click Save, Save in: My Documents, File name:
Test1, Save as type: Drawing (*.vsd), click the Save button.
4. Click on the Insert menu and click Object…, under ‘Object type’ click
Microsoft Equation 3.0, make sure Create new is selected and Display as
icon is unchecked. Click OK.
5. Click on Greek characters (uppercase), click I, click on the File menu,
and click Save.

The drawing saves without error.

In Visio, under the Help menu, click About Microsoft Office Visio. You
should see a number in parenthasis like (11.8161.8172) SP3. If you don’t
see SP3, then you’re not on any service pack. Also, confirm that you have
Equation Editor 3.1 by inserting a new Microsoft Equation, and clicking on
the Help menu and clicking About Microsoft Equation Editor.

Best Regards,

Aaron Rykhus, MCP, MCDST
Online Support Engineer
Microsoft Corporation

Advertisements

Theresa Hardy


  • #7

Hello, I know this is an old post, but I was having this error as well. I
was linking external data (in Excel) to Visio shapes. It worked and saved
fine until I added a new row to my Excel file that had a negative value in
it. As soon as I took out the value in the Excel file it worked perfectly.

Alick LOk


  • #8

Hello Mr, Rhykhus,

I tried to ‘save as’ a new file name I got error ‘visio internal error
#3400′ action 1005: Save As. By closing and re-openning and restarting visio
does not solve the problem. My get around: Made the change to the visio chart
and save (sa the same name).
———————
The other server boot error also getting the ‘write delay error’ resulting:
«to an an existing blade that has been up for a few months. We started
getting write delay errors and now the system hangs at the Windows splash
screen on boot.»

So this is not just a visio ‘write delay error’ to visio only, rather I
syspect it is a Window design/engineering problem that should be escalated to
Microsoft Developer Team.

Many thanks

Alick Lok — SAN Storage Admin and Mainframe Systems Programmer.

Advertisements

Aaron Rykhus [MSFT]


  • #9

That error 3400 is a general OLE error. Hard to say what’s going on without
actually seeing the file. Another thing you could try that I don’t think
was mentioned was saving the file as an XML Drawing (*.vdx), if you can
save to that format it may have been corruption in the binary OLE data in
the file.

I’m not sure what you are referring to with the ‘write delay error’
remarks, were you getting that anywhere while working in Visio?

Best Regards,

Aaron Rykhus, Visio Support
Microsoft Corporation

  •  
  • visio

  • document-library

  • visio-services

  •  
  •  | 

  •  

Question

Backstory: For our company intranet we wanted to add an employee seating chart feature so that employees can see where other employees in the building sit. I created a document library to store the floor plans as Visio files so that they can be viewed by the employees on another page using the Visio Web Access webpart.

Problem: The initial save to the document library worked but whenever I try to check the Visio file into the document library it gives me the following error:

Internal Error #3400 Action 1787: Check in file First try closing and
reopening the file. Next try to restart Visio

I found a solution on the Microsoft forums saying that I need Visio Premium instead of Professional but I have Premium so that is not the problem.

Solution 2

I found this blog entry which talks about required fields being missing when trying to submit changes. However, I looked at the default document library columns and none of them appeared to be required. Finally, I checked the «Info» page in Visio itself where you have to check-in the document and I found a bunch of properties on the right that were not all filled in.

The image below shows the properties inside the red box. I made sure that all of them were filled in and after that I no longer received an error when checking in the Visio drawing.

Visio Page

OTHER TIPS

Although the answer above may have solved the issue, the underlying problem is due to Required List Content Types that your company may have required for your Documents.

For SharePoint 2013 (where I had the same issue):

1) In the Document Library where you are storing the Visio file, click on the «LIBRARY» tab at the top of the screen and select «Library Settings«.

2) Under «Content Types» select «Document» or «Company Document» or whatever the Default Content Type is.

3) You may see some Columns (Properties) which the Site Owner has determined are Required. These are the Properties which must be populated for the Visio File itself in the Document Library.

4) Return to your Document Library and Select (checkmark) your Visio File. Click on the «FILES» tab at the top of the screen and select «Edit Properties«.

5) Any Line that has an asterisk (*) against it is a Required Property.

Populate all the «*» lines and you will no longer have the «Internal Error #3400» problem when Saving and Checking-In the Visio File to your SharePoint site.

I was able to check in the file once I populated the required metadata. It would be much more helpful if Visio opened the document panel with the required fields as most other Office applications do.

Tengo el siguiente formulario en un modal:

Code:

<!-- Falta -->
<div class="modal fade" id="faltaModal" role="dialog" aria-hidden="true">
  <div class="modal-dialog modal-md" role="document">

    <form role="form" method="post" id="formFalta">
      <div class="modal-content">

        <div class="modal-header">
          <h4 class="modal-title"><b>FALTA</b></h4>
          <button type="button" class="close" data-dismiss="modal" aria-label="Close"><span aria-hidden="true">&times;</span></button>
        </div>

        <div class="modal-body">
          <div class="form-row">
            <div class="col-md-5 mb-3">
              <input class="form-control" type="text" name="fecha" id="modalFecha" readonly>
              <input class="form-control" type="number" name="no_empleado" id="no_empleado1" readonly>
            </div>
          </div>
        </div>
        
        <div class="modal-footer">
          <button type="button" class="btn btn-secondary back-to-first-modal">REGRESAR</button>
          <button type="submit" class="btn btn-primary">GUARDAR</button>
        </div>

      </div>
      
    </form>
  </div>
</div>

Tengo este código JavaScript:

Code:

$('#formFalta').submit(function(event) 
{
  event.preventDefault(); // Evita el envío normal del formulario
  
  //var formData = $(this).serialize(); // Serializa los datos del formulario

  // Obtén los valores del formulario
  var fecha1 = $('#modalFecha').val(); 
  var no_empleado1 = $('#no_empleado1').val(); 
  
  $.ajax(
  {
    type: 'POST',
    url: 'controladores/faltas.controlador.php',
    data: 
    {
      accion: 'crear',
      fecha: fecha1, 
      no_empleado: no_empleado1
    },
    success: function(response) 
    {
      alert(response); // Muestra la respuesta del servidor (éxito o error)
      $('#faltaModal').modal('hide'); // Cierra el modal de faltas

      calendar.addEvent(
      {
        title: 'FALTA',
        start: selectedDate, // Usa la fecha seleccionada
        backgroundColor: 'red',
        borderColor: 'red',
        color: 'white'
      });
    }
  });
});

Y este es mi archivo «faltas.controlador.php»:

Code:

<?php

class ControladorFaltas
{
require_once "conn.php";

    static public function manejarSolicitud()
    {
        $respuesta = array();

        if ($_SERVER["REQUEST_METHOD"] == "POST") 
        {
            if (isset($_POST["accion"]) && $_POST["accion"] == "crear") 
            {
                // Acción 'crear' detectada, llama a la función ctrCrear
                $respuesta = self::ctrCrear();
            }
            else 
            {
                $respuesta["error"] = "Acción no válida.";
            }
        }
        else
        {
            $respuesta["error"] = "Solicitud no válida.";
        }

        echo json_encode($respuesta);
    }

    static public function ctrCrear()
    {
        $respuesta = array();

        if (isset($_POST["fecha"]) && isset($_POST["no_empleado"])) 
        {
            $fecha = $_POST["fecha"];
            $no_empleado = $_POST["no_empleado"];
            $registro = date("Y-m-d H:i:s");
            $num = 1;

            // Realiza la conexión a la base de datos
            $conexion = conn::conn();

            // Prepara la consulta SQL para insertar en la tabla "faltas"
            $sql = "INSERT INTO faltas (inicial, no_empleado, registro, captura) VALUES ('$fecha', '$no_empleado','$registro', '$num')";

            // Ejecuta la consulta
            if ($conexion->query($sql) === TRUE) 
            {
                // Obtiene el ID generado automáticamente para la última inserción en "faltas"
                $id_movimiento = $conexion->insert_id;

                // Prepara la consulta SQL para insertar en la tabla "events"
                $sql_events = "INSERT INTO events (id_movimiento, no_empleado, start_event, title) VALUES ('$id_movimiento', '$no_empleado', '$fecha', 'FALTA')";

                // Ejecuta la consulta para insertar en "events"
                if ($conexion->query($sql_events) === TRUE) 
                {
                    $respuesta["mensaje"] = "Registro de falta insertado correctamente en ambas tablas (faltas y events)";
                } 
                else 
                {
                    $respuesta["error"] = "Error al insertar el registro en la tabla 'events': " . $conexion->error;
                }
            } 
            else 
            {
                $respuesta["error"] = "Error al insertar el registro en la tabla 'faltas': " . $conexion->error;
            }

            // Cierra la conexión a la base de datos
            $conexion->close();
        }

        echo json_encode($respuesta);
    }
}

// Llama a la función manejarSolicitud para procesar la solicitud
ControladorFaltas::manejarSolicitud();

?>

De esta manera todo funciona correctamente. La inserción en la base de datos se ejecuta sin problema. El problema surge cuando quiero darle al código un enfoque más orientado al patrón MVC. Mi archivo «faltas.controlador.php» se vería así:

Code:

<?php

require_once 'modelos/faltas.modelo.php';

class ControladorFaltas
{
    static public function manejarSolicitud()
    {
        $respuesta = array();

        if ($_SERVER["REQUEST_METHOD"] == "POST") 
        {
            if (isset($_POST["accion"]) && $_POST["accion"] == "crear") 
            {
                // Acción 'crear' detectada, llama a la función ctrCrear
                $fecha = $_POST["fecha"];
                $no_empleado = $_POST["no_empleado"];
                $respuesta = ModeloFaltas::crearFalta($fecha, $no_empleado);
            }
            else 
            {
                $respuesta["error"] = "Acción no válida.";
            }
        }
        else
        {
            $respuesta["error"] = "Solicitud no válida.";
        }

        echo json_encode($respuesta);
    }
}

ControladorFaltas::manejarSolicitud();

?>

Y mi archivo «faltas.modelo.php» se vería así:

Code:

require_once "conn.php";
<?php

class ModeloFaltas
{
    public static function crearFalta($fecha, $no_empleado)
    {
        $respuesta = array();

        $registro = date("Y-m-d H:i:s");
        $num = 1;

        // Realizar la conexión a la base de datos
        $conexion = conn::conn();
        // Preparar la consulta SQL para insertar en la tabla "faltas"
        $sql = "INSERT INTO faltas (inicial, no_empleado, registro, captura) VALUES ('$fecha', '$no_empleado','$registro', '$num')";

        // Ejecutar la consulta
        if ($conexion->query($sql) === TRUE) 
        {
            // Obtener el ID generado automáticamente para la última inserción en "faltas"
            $id_movimiento = $conexion->insert_id;

            // Preparar la consulta SQL para insertar en la tabla "events"
            $sql_events = "INSERT INTO events (id_movimiento, no_empleado, start_event, title) VALUES ('$id_movimiento', '$no_empleado', '$fecha', 'FALTA')";

            // Ejecutar la consulta para insertar en "events"
            if ($conexion->query($sql_events) === TRUE) 
            {
                $respuesta["mensaje"] = "Registro de falta insertado correctamente en ambas tablas (faltas y events)";
            } 
            else 
            {
                $respuesta["error"] = "Error al insertar el registro en la tabla 'events': " . $conexion->error;
            }
        } 
        else 
        {
            $respuesta["error"] = "Error al insertar el registro en la tabla 'faltas': " . $conexion->error;
        }

        // Cerrar la conexión a la base de datos
        $conexion->close();
        
        return $respuesta;
    }
}

?>

Al intentar con el enfoque MVC, no funciona. ¿Qué estoy haciendo mal? Recibo este error: «500 (Error interno del servidor)».

Понравилась статья? Поделить с друзьями:
  • Внутренняя ошибка visio 2407
  • Внутренняя ошибка 2771
  • Внутренняя ошибка компилятора c clr
  • Внутренняя ошибка 2761
  • Внутренняя ошибка csp 0x80090020 при шифровании криптоарм